Hardware roadmap

roadmap_read answers the calendar quarter in which a GPU model is expected to land on the platform. The quarter is an expectation from National Compute's capacity planning. It is never a commitment. The answer carries no quantity, no date inside the quarter and no source.

capacity planning ──▶ platform roadmap ──▶ roadmap_read ──▶ your agent
    (internal)          GPU model + expected quarter, nothing else

The tool lives on the MCP server. It is read only and single phase. No confirm_token is involved. Every signed in member reads the same list. The answer is not scoped to an organization.

Arguments

Argument	Values	Applies to
gpu_model	a GPU model name as the capacity reads spell gpu_model; matched case insensitively	optional; omit it for the whole list

The answer

A request for one model carries {"gpu_model": "<model>"}. Its answer:

{
  "as_of": "2026-09-24T03:50:00Z",
  "age_s": 412,
  "entries": [{"gpu_model": "<model>", "expected_quarter": "2028-Q3"}],
  "note": "Expected landing quarters from National Compute's planning. An expectation, not a commitment: quantities, dates, sources and sites are not published. Ask marshall to record your interest and the team follows up."
}

Field	What it carries
as_of	when the platform last refreshed the roadmap, ISO 8601 UTC
age_s	the age of that refresh, seconds
entries	one entry per GPU model, each {gpu_model, expected_quarter}
expected_quarter	a calendar quarter in UTC, as YYYY-Qn
note	how to read the answer, in one short paragraph

Read the example as: planning expects that model to land in the third quarter of 2028, between July and September. The values are illustrative; the live answer names real models. Nothing in the answer narrows a quarter further. The answer does not say how many GPUs, on which day, or from where.

Each GPU model appears once. The quarter shown is the earliest one planning expects for that model. Capacity that has already landed is never a roadmap entry. The capacity reads name the GPU class each cluster prices today as gpu_model. A model with no published landing answers entries: []. Its note says that no landing is published for that model. That is a valid answer: nothing firm is planned for it.

What the roadmap publishes

Published	Never published
the GPU model	quantities
the calendar quarter	exact dates
	providers or suppliers
	sites or regions
	deal status
	customers
	prices

The right column is absent from the wire rather than redacted from it. The tool's output is a fixed mapping of the two published fields. No other value can appear on any question. An agent pressed for a count, a date or a supplier has nothing to read.

Ask marshall to record your interest in a GPU model. The team follows up from there. That request works for a model with no entry as well.

Freshness

The platform refreshes the roadmap from its planning data at regular intervals. It keeps the last good copy. When a refresh fails, the last good copy stays in place. age_s then keeps growing. Read age_s before you quote an old answer.

Refusals

Code	Status	Meaning
roadmap-unavailable	503	the roadmap feed has not loaded; retry later

A roadmap that has never loaded is always a refusal. The tool never presents it as an empty list. An empty entries on a successful answer means nothing firm is planned. With gpu_model given, the empty list speaks for the named model. Without it, the empty list speaks for every model.