Skip to main content
Glama

The MW Desk Data Center API

dc_legislation

Data center bills, ordinances and moratoriums with status and next action, with sources. Filters: state, 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_legislation"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
stageNo
stateNo
countyNo
marketNo
min_mwNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description does useful work by disclosing cost (1 credit/$0.01 per call) and the API-key requirement, which materially affects invocation planning. It says nothing about result volume, pagination, ordering, or whether limit truncates silently — significant gaps for an unannotated read tool.

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?

Two tight sentences with the resource front-loaded and cost appended; nothing is padding. The phrase 'Costs 1 credits' is a minor grammatical blemish but costs no clarity.

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

Completeness2/5

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

For a six-parameter tool with zero schema description coverage, no annotations, and no output schema, the description is under-built: four filters go entirely unexplained, and there is no hint about what a returned record looks like beyond the tagline.

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 six parameters exist, yet the description explains only state and limit (with a max of 50). The stage, county, market, and min_mw filters carry no meaning in either the schema or the text, and the fact that limit and min_mw are typed as strings is left unaddressed.

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?

The description names a specific resource set — data center bills, ordinances and moratoriums — plus what accompanies each record (status, next action, sources). That is clear enough to distinguish it from dc_deals or dc_power, though it never states an explicit verb and never differentiates itself from siblings by name.

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

Usage Guidelines2/5

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

It lists two filters and a price, but gives no when-to-use guidance, no when-not-to-use, and no routing to or away from the sibling tools. An agent must infer from the noun phrase alone whether this or dc_projects is the right call.

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