Skip to main content
Glama

supply-chain-intelligence

by io.github.SupplyMaven-SCR
OverviewDiscussionsAdmin

get_data_center_hub_load

Grid load for five US data center hub zones, built from EIA-930 hourly demand and delivered as daily or monthly series. Hubs: DOM (Dominion Virginia Power zone, PJM), NCEN (North Central, ERCOT), CE (Commonwealth Edison zone, PJM), PGAE (Pacific Gas and Electric, CAISO), ZONJ (New York City, NYISO). Daily rows: date, average MW, overnight floor MW (the day's minimum hour), zone hours, matched hours, status, and share of the parent grid. Monthly rows: average MW, overnight floor MW, share of parent, trailing 12-month average and overnight floor with their growth on the trailing 12 months a year earlier, and the count of complete days each figure used. Basis: EIA-930 hourly demand; UTC calendar days and months; days with fewer than 20 reported zone hours excluded; revisions not applied to the zone series. Signal tier.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hubNoHub zone code: DOM, NCEN, CE, PGAE or ZONJ.
endDateNoDaily: YYYY-MM-DD (default the latest stored day; at most 366 days per request). Monthly: YYYY-MM (default the latest UTC month that has ended).
startDateNoDaily: YYYY-MM-DD (default 30 days before endDate). Monthly: YYYY-MM (default 24 months before endDate).
granularityNo'daily' or 'monthly'. Default monthly.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does substantial work: it names the data basis (EIA-930), the time basis (UTC days/months), the exclusion rule (<20 zone hours), and the caveat that revisions are not applied. It does not state auth or rate limits, and the trailing tagline 'Signal tier' is opaque.

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?

Front-loads the purpose, then the hub roster, then the row schemas, then the basis caveats. Efficient for the amount of information conveyed, with only minor density issues in the monthly-field sentence.

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

Completeness4/5

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

Given no output schema and no annotations, the description supplies the data lineage, record fields, time semantics, and quality rules an agent needs to interpret results. It stops short of stating return format mechanics or any permissions/rate context.

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?

Schema coverage is 100% and the schema already documents hub codes, date formats, and granularity defaults thoroughly. The description's hub list and field enumeration add little beyond the schema, so baseline 3 applies.

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?

States the exact resource (grid load for five named US data center hub zones), the source (EIA-930 hourly demand), and the output form (daily or monthly series). An agent cannot confuse this with commodity_price_monitor or get_energy_breakdown.

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

Usage Guidelines3/5

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

Implies the usage domain (data center hub zone power demand) but never says when to pick this over the sibling energy tools or what conditions call for daily vs monthly. No exclusions are given.

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

All supply-chain-intelligence toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources