Skip to main content
Glama

The MW Desk Data Center API

dc_power

Power and siting context by county: project count, known MW, power status mix, utilities, opposition count, sources. Filters: state, county, limit (max 50). Costs 1 credits ($0.01) per call; needs an API key.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
stageNo
stateNo
countyNo
marketNo
min_mwNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the behavioral burden; it usefully discloses that each call costs 1 credit ($0.01), requires an API key, and caps limit at 50. It does not describe pagination, error behavior, or explicitly state read-only semantics, so it is informative but not complete.

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?

Two compact sentences use colon-delimited lists and front-load the returned fields before filters and cost. There is little wasted wording, though '1 credits' is a minor grammar issue.

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

Completeness3/5

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

For a six-parameter query tool with no output schema and no annotations, the description supplies the returned fields, cost, auth requirement, and three filter semantics. It remains incomplete because half the parameters are unexplained and there is no output format or pagination detail.

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

Parameters2/5

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

Schema description coverage is 0%, and the description only explains state, county, and limit (max 50). It leaves stage, market, and min_mw completely undocumented, so an agent cannot infer their meaning or accepted formats from the definition.

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 data resource, 'Power and siting context by county,' and enumerates returned metrics such as project count, known MW, power status mix, utilities, opposition count, and sources. This is clear enough to identify the tool, but it does not explicitly differentiate it from siblings like dc_projects or dc_pricing.

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 filter list for state, county, and limit implies usage for geographic power and siting queries, but there is no explicit 'use when' or 'use instead of' guidance. No alternatives or exclusions are mentioned.

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.

Resources