Skip to main content
Glama
azmartone67

DC Hub — Data Center & Energy Intelligence

Interconnection Queue

get_interconnection_queue
Read-onlyIdempotent

Get queued generation capacity (GW) per ISO and ERCOT's data-center large-load queue (225+ GW in process) for AI/data-center load saturation and site-selection intel.

Instructions

ISO interconnection queue snapshot: total queued GENERATION capacity (queued_load_total_gw, GW) per ISO from each ISO's public queue. For ERCOT it ALSO returns the large-load (data-center-driven) interconnection queue in queued_load_data_center_gw — >225 GW in process / ~9 GW approved-to-energize (ERCOT's published Q1-2026 figure; ERCOT is the only ISO that publishes a comparable large-load feed, so other ISOs' data_center_gw is null), with provenance in top_subregions. Sources: ERCOT GIS + Large Load Integration, PJM/MISO/SPP/CAISO/NYISO/ISO-NE public queues. Pass iso=ERCOT (or any of 7) to drill down. ★ The projects field CHANGES SHAPE with the call: with iso= it is an ARRAY of per-project rows; with iso omitted it is the all-ISO SUMMARY OBJECT {total, tracked, by_iso_count, top, note} and carries no per-project rows — check the type before indexing. Use for queue-depth site-selection and AI/data-center-load saturation intel (the ERCOT 225 GW number is the headline large-load figure no other source surfaces machine-readably). Do NOT use for a single-site time-to-power read (use get_grid_intelligence) or forward-looking emergence (use grid_transition_radar); this is the ISO-level queue snapshot.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
isoNoISO/RTO grid region to drill into: ERCOT, PJM, MISO, CAISO, SPP, NYISO, ISONE; omit for the all-ISO snapshot

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
vNoVerification flag for the snapshot
isoNoISO/RTO this snapshot covers (per-ISO drill-down form)
as_ofNoQueue snapshot date
quotaNoCaller quota state (remaining calls, tier) when available.
_entityNoPayload class discriminator (e.g. facility|market|iso_grid|queue_results|deal|report|response) — branch on this before parsing the rest.
citationNoMachine-readable citation: how to attribute DC Hub (dchub.cloud) for this payload. Normally an OBJECT {source, url, license, cite_as, retrieved_at}; a bare string is accepted and carries the attribution line itself.
projectsNoSHAPE DEPENDS ON THE CALL: with iso= this is an ARRAY of queued generation projects (largest / most recent first); with iso omitted it is the all-ISO SUMMARY OBJECT {total, tracked, by_iso_count, top, note} — per-project rows are not returned for the all-ISO snapshot. Check the type before indexing.
provenanceNoCollection-level provenance block: {source, method, as_of, verification_counts, cite_url_template, license, cite_as}. Quote the verification level when citing.
source_urlNoQueue source URL
_front_doorNoIn-band front-door hint (first workflow-entry tool of a session): call plan_query(intent) first for the ordered multi-step plan.
source_nameNoQueue source name
_return_loopNoSuggested next-session delta call (get_changes since=24h) so you pull only what changed.
project_countNoProjects in the queue snapshot
top_subregionsNoProvenance / sub-region breakdown for the large-load figure (ERCOT)
queued_load_total_gwNoTotal queued GENERATION capacity in this ISO, GW
new_applications_q_gwNoNew queue applications in the latest period, GW (when published)
new_applications_periodNoPeriod the new-applications figure covers
site_evaluation_handoffNoPre-built follow-up calls (analyze_site / get_water_risk args) when the payload carries coordinates — an array of {tool, parameters, why} entries.
queued_load_dc_share_pctNoERCOT only: data-center share of queued load, %
historical_completion_pctNoShare of queued projects that historically complete, % (when published)
queued_load_data_center_gwNoERCOT only: large-load (data-center-driven) queue, GW — null for ISOs that publish no comparable feed
Install Server

TDQS

A4.9/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Even with readOnly/idempotent/non-destructive annotations covering the safety profile, the description discloses critical dynamic behavior beyond those: 'The `projects` field CHANGES SHAPE with the call' and gives the specific array-versus-summary-object shapes. It also surfaces ERCOT-specific data provenance and the null behavior for other ISOs, which an agent must know to interpret results safely.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Though dense, the description is carefully ordered: core function, key exception, sources, parameter usage, shape-change warning, use cases, and exclusions. The starred shape warning is front-loaded at the exact point where it matters, and every sentence carries load-bearing information with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description need not enumerate return fields, but it still covers the purpose, the parameter's effect, the only ISO with non-null data_center_gw, the provenance, and explicit sibling routing. The tricky `projects` shape change is called out even though it risks being redundant with an output schema, which demonstrates thoroughness for callers.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single iso parameter is already fully documented in the schema with allowed values and omit behavior (100% coverage), so the baseline is 3. The description adds value by linking the parameter to the dynamic shape of `projects` — 'with iso= it is an ARRAY...; with iso omitted it is the all-ISO SUMMARY OBJECT' — giving the parameter semantic weight beyond the schema's field listing.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a crisp verb+resource+scope: 'ISO interconnection queue snapshot: total queued GENERATION capacity ... per ISO.' It immediately distinguishes itself from sibling tools by name (get_grid_intelligence, grid_transition_radar) and specifies the exact fields returned, so an agent can tell what it does without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage guidance is explicit and bidirectional: 'Use for queue-depth site-selection and AI/data-center-load saturation intel' and 'Do NOT use for a single-site time-to-power read (use get_grid_intelligence) or forward-looking emergence (use grid_transition_radar).' It also instructs how to vary the call ('Pass iso=ERCOT ... to drill down'), leaving no ambiguity about when to choose this tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/azmartone67/dchub-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server