Skip to main content
Glama
azmartone67

DC Hub — Data Center & Energy Intelligence

Get Iso Context

get_iso_context
Read-onlyIdempotent

Get a token-budgeted whole-grid briefing for any US ISO/RTO: live demand, fuel mix, LMP, queue depth, economics, and news—all with citations and timestamps in one call.

Instructions

Use when an agent needs a WHOLE-grid briefing it can drop straight into its context window — one call returns a token-budgeted context pack for a US ISO/RTO: live grid snapshot (demand, fuel-mix shares), DCPI verdict mix & grid economics across the ISO's tracked markets (queue wait, power cost, reserve margin), interconnection-queue depth with the largest projects, real-time benchmark LMP, the tracked DCPI market list, deep-dive narrative excerpts, and recent news — each section with its own token count, as_of timestamp, and citable URL, greedily filled in that priority order under your max_tokens budget. Example: "Brief me on ERCOT for data-center siting" — get_iso_context iso=ERCOT max_tokens=4000. Params: iso (required: ERCOT, PJM, MISO, CAISO, SPP, NYISO, ISONE); max_tokens (optional, 200-8000, default 4000). Returns {sections:[{id,title,text,tokens,as_of,cite}], used_tokens, omitted}. Do NOT use for raw single-ISO telemetry (use get_grid_data), the per-ISO decision brief with headroom/TTP (use get_grid_intelligence), multi-ISO scalar comparison (use compare_isos), or non-US grids (use get_grid_scoreboard); this is the narrative briefing pack. Cite "DC Hub (dchub.cloud)".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
isoNoISO/RTO grid region (required): ERCOT, PJM, MISO, CAISO, SPP, NYISO, ISONE
max_tokensNoToken budget for the pack, 200-8000 (default 4000); sections are filled in priority order until the budget is spent

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
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.
provenanceNoCollection-level provenance block: {source, method, as_of, verification_counts, cite_url_template, license, cite_as}. Quote the verification level when citing.
_front_doorNoIn-band front-door hint (first workflow-entry tool of a session): call plan_query(intent) first for the ordered multi-step plan.
_return_loopNoSuggested next-session delta call (get_changes since=24h) so you pull only what changed.
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.
Behavior5/5

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

Beyond the readOnly/idempotent hints in annotations, the description discloses the token-budgeting behavior ('greedily filled in priority order'), the per-section metadata (token count, as_of, cite URL), the exact return structure, and the citation requirement. This gives the agent a full model of what to expect.

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

Conciseness4/5

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

The description is long yet structured: starts with a clear use case, then content list, example, parameters, return format, and exclusions. While somewhat verbose, every part contributes essential detail for a complex tool. It could be tightened without losing value, hence 4.

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?

The description is highly complete: it covers purpose, usage triggers, parameter details, return format (with section structure), exclusions/alternatives, and even a citation instruction. Given the tool's complexity and the presence of an output schema in prose, no important context is missing.

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

Parameters3/5

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

Both parameters are fully described in the input schema (iso with enum values, max_tokens with range/default/priority behavior), so the description does not add new semantic information. It repeats the schema content in prose and provides an example, but no additional meaning beyond that.

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 clearly defines the tool as returning a token-budgeted context pack for a US ISO/RTO, listing specific content sections (grid snapshot, DCPI metrics, queue depth, LMP, news). It explicitly distinguishes from siblings by stating 'Do NOT use for raw single-ISO telemetry (use get_grid_data)...' making purpose and differentiation unmistakable.

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?

Provides explicit use case ('Use when an agent needs a WHOLE-grid briefing'), a concrete example ('Brief me on ERCOT for data-center siting'), and a clear list of exclusions with alternative tools (get_grid_data, get_grid_intelligence, compare_isos, get_grid_scoreboard). This goes far beyond basic guidance.

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

Install Server

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