Skip to main content
Glama

DC Hub — Data Center Site Selection & Colocation: Electricity, Power Grid, Gas, Fiber

Grid Scoreboard

get_grid_scoreboard
Read-onlyIdempotent

GLOBAL grid scoreboard — 9 US grid operators (PJM, ERCOT, CAISO, MISO, SPP, NYISO, ISO-NE, BPA, TVA) + Great Britain (NESO) + the European bidding zones (Germany, France, Netherlands, Italy/Milan, Spain, Poland, Switzerland, Portugal, the Nordics + Central/Eastern Europe — via ENTSO-E; the exact live-vs-configured count is in counts_basis.eu_zones_live / eu_zones_configured, measured per call rather than asserted here) + Taiwan (Taipower) + Japan (OCCTO areas) + South Korea (KPX) + Brazil SIN (ONS), ranked side-by-side on each feed's LATEST PUBLISHED reading: renewable share %, gas share %, full fuel mix (gas/nuclear/coal/wind/solar/hydro MW), and demand. ★FRESHNESS IS NOT UNIFORM and every row says so: each carries mix_period, mix_age_hours and freshness_basis. The US rows come from EIA hourly RTO, which publishes the FUEL-TYPE BREAKDOWN several hours behind aggregate demand — an overnight mix reading is routinely 18-24h old (it will show near-zero solar) while demand on the same row is ~1-2h old. Read mix_age_hours before narrating any row as current, and NEVER describe a row as the mix "right now" unless its mix_age_hours is small; demand_period and mix_period are separate clocks and the row reports both plus demand_vs_mix_lag_hours. One call answers "which grid worldwide is greenest, or most gas-reliant, for siting a data center?" — vs compare_isos (pairwise) or get_grid_data (single ISO). Every ranked grid scores renewable_share_pct as wind+solar+hydro (apples-to-apples across all feeds; geothermal is reported separately and, where it exists, also as renewable_share_incl_geothermal_pct — note get_grid_intelligence uses that geothermal-inclusive figure for US ISOs); Brazil ranks by renewable share but reports NO gas share (ONS bundles gas/coal/oil/biomass into one thermal figure — never presented as gas); Australia NEM (AEMO) + Singapore (EMA) are listed unranked in partial_grids (no full fuel split — kept honest). Source: US = EIA hourly RTO; GB = Elexon Insights; EU = ENTSO-E Transparency; TW = Taipower; JP = TSO eria_jukyu CSVs; KR = KPX real-time; BR = ONS Balanço de Energia; AU = AEMO NEM; SG = EMA NEMS — all live via DC Hub, greenest-first. Quote with attribution to DC Hub (CC-BY-4.0). Answers "which grid is cleanest right now", "how is ERCOT doing at this moment". Try: get_grid_scoreboard.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okNotrue when the scoreboard build succeeded
countNoRanked grids — the long-standing alias of zones_ranked (NOT grids.length, which also carries the unrankable rows)
gridsNoFully-ranked grids, greenest (highest renewable share) first — US ISOs + GB + EU zones + TW + JP + KR + BR
quotaNoCaller quota state (remaining calls, tier) when available.
sourceNoUpstream feeds behind the rows in THIS response, generated (EIA hourly RTO, Elexon, ENTSO-E, Taipower, OCCTO, KPX, ONS, AEMO, EMA)
_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.
coverageNoCoverage line GENERATED from the rows that actually ranked — a feed that returned nothing is absent from it
freshnessNoRows are each feed's LATEST PUBLISHED reading, NOT a synchronized snapshot: {basis, us_mix_source, stale_mix_threshold_hours, stale_mix_rows[], how_to_read}. Read this before narrating any row as current
ranked_byNoRanking criterion (renewable share = wind+solar+hydro, greenest first) plus the full definition — identical on every feed, geothermal and biomass excluded from the numerator
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.
counts_basisNoWhat each count actually counts, plus per_source rows, eu_zones_live vs eu_zones_configured, and the unranked/unavailable tallies
zones_rankedNoGrid rows carrying a live renewable_share_pct, i.e. the ranked set
partial_gridsNoGrids listed UNRANKED because the feed has no full fuel split (Australia NEM, Singapore EMA)
eu_gas_contextNoEU gas-flow context: {active_countries, total_throughput_gwh_per_day, unit, source, note}
deep_intelligenceNoPointers to the deeper per-ISO / per-site tools to call next
independent_sourcesNoDistinct upstream feeds behind those rows — far below zones_ranked because every EU bidding zone comes from ONE feed (ENTSO-E). null when the per-source tally failed
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.
us_interconnection_queue_gwNoTotal queued generation across the 7 US ISO interconnection queues, GW

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

The description discloses critical behavioral traits beyond the readOnlyHInt: non-uniform freshness, mix_age_hours routinely 18-24h old, separate demand/mix clocks, Brazil's missing gas share, and partial_grids for AUS/SG. It tells the agent to read mix_age_hours before narrating a row as current, adding substantial safety value.

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 and dense, but every sentence carries needed caveat or context. It front-loads the core purpose and the 'freshness is not uniform' warning early. It is not concise in word count, but it earns its length given the complexity.

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?

For a zero-parameter, read-only tool with a rich output, the description covers scope, data sources, ranking method, exclusions, geothermal nuance, freshness semantics, licensing, and example questions. An agent has everything needed to call it and interpret results correctly.

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?

There are zero parameters, so the schema has nothing to document. The description compensates by explaining what the output contains (renewable share %, fuel mix, gas share, mix_age, demand_vs_mix_lag), which sets correct expectations despite no output schema properties.

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 states a clear verb+resource: it fetches a global ranked grid scoreboard. It names all covered regions/operators and explicitly contrasts with siblings ('vs compare_isos (pairwise) or get_grid_data (single ISO)'), so an agent can distinguish it from the many grid-related tools.

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?

It states specific use cases ('which grid worldwide is greenest, or most gas-reliant, for siting a data center?') and names alternatives: compare_isos for pairwise, get_grid_data for single ISO. It also warns about freshness caveats so an agent knows when to rely on the ranking vs. drill into details.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation2/5

Multiple tools occupy nearly identical semantic space: search/search_facilities/search_intelligence/semantic_search all retrieve data, and analyze_site/compare_sites/score_facility/get_composite_site_score/rank_sites all score or rank locations. Despite extensive disambiguation in the descriptions, the boundaries are subtle enough that an agent will likely misroute queries. Account and meta tools (claim_free_key, bind_email, unlock_more_data, subscribe_digest, recover_my_key, execute_plan, plan_query, discover_tools) add further selection noise.

Naming Consistency4/5

The vast majority of tools follow a clear snake_case verb_noun convention (get_*, search_*, list_*, set_*, save_*, compare_*, analyze_*, rank_*, plan_*). A few noun-phrase names break the pattern (deal_autopsy, hyperscaler_deals, grid_transition_radar, site_selection_canvas, standing_intent, ai_capacity_index), but these are still readable and discoverable.

Tool Count1/5

83 tools is an extreme count for any server, far beyond the 25+ threshold that already signals bloat. The domain is broad, but the catalog is inflated by overlapping variants, multiple meta-tools (execute_plan, plan_query, discover_tools, get_agent_registry, get_backup_status, summarize_for_citation), and account/upgrade plumbing (claim_free_key, bind_email, recover_my_key, unlock_more_data, subscribe_digest). This imposes heavy context and selection costs on agents.

Completeness5/5

The data-center siting domain is covered exhaustively: single-site scoring, market ranking, grid/gas/fiber/water/climate/disaster/tax/permitting intelligence, interconnection queues, construction pipeline, deals/news, saved-site monitoring, alerts, research dossiers, and citation support. Every workflow has a continuation path, so agents will not hit dead ends.