Skip to main content
Glama
Sign In

Dchub

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Dchub Get Grid Data

dchub_get_grid_data
Read-onlyIdempotent

Live electricity grid data for one grid (DC Hub): fuel mix and demand for US ISOs (PJM, ERCOT, CAISO, MISO, SPP, NYISO, ISO-NE), utility balancing authorities, and international grids.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "iso": "PJM"
    },
    "name": "dchub_get_grid_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
isoYesGrid code, e.g. PJM, ERCOT, CAISO
metricNoOptional metric
periodNoOptional period

Output Schema

NameRequiredDescriptionDefault
resultNo
sourceNo
previewNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the bar is lower. The description adds one genuinely useful behavioral fact — the data is 'live' rather than historical — but discloses nothing about freshness/lag, update cadence, coverage gaps, or how the open-world external dependency can fail.

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?

A single front-loaded sentence with no filler; the resource and the grid enumeration come first. Dense but slightly overloaded as one run-on sentence, with no clear enumeration formatting for the ISO list.

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?

With a full output schema and rich annotations, the description only needs to establish purpose and scope, which it does. The remaining gap is that valid values for the two optional parameters and acceptable grid codes beyond the examples are left unaddressed, so an agent must guess at `period` semantics.

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 description coverage is 100%, so baseline is 3. The description does add value for the `iso` parameter by listing the supported grid families (PJM, ERCOT, CAISO, MISO, SPP, NYISO, ISO-NE, plus BAs and international grids) and hints at `metric` via 'fuel mix and demand', but `period` remains completely opaque in both schema and description.

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

Purpose4/5

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

States a specific resource and scope: live fuel-mix and demand data for a single grid, with the supported grid universe enumerated (US ISOs, utility balancing authorities, international grids). An agent can tell it retrieves current grid state rather than market intel, but the description never explicitly contrasts it with dchub_get_market_intel or dchub_source_capacity.

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?

The phrase 'live electricity grid data for one grid' implies the usage context (real-time operational data for a named grid), but there is no explicit when-to-use guidance, no exclusions, and no mention of the sibling tools an agent should prefer for adjacent questions like market pricing.

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

All Dchub 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