Skip to main content
Glama

The MW Desk Data Center API

dc_projects

US data center projects from public sources: MW, stage, power status, utility, opposition, source URLs. Filters: state (2-letter), county, stage, min_mw, limit (max 50). Costs 2 credits ($0.02) 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_projects"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
stageNo
stateNo
countyNo
marketNo
min_mwNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the disclosure burden and does it well: it reveals the cost model (2 credits / $0.02 per call), the authentication requirement (API key), the public-source provenance, and the hard cap of 50 results. It omits pagination/offset behavior and error handling, so it stops short of full transparency.

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 tightly packed sentences with zero filler: the resource and payload come first, then filters, then cost/auth. Every clause carries information an agent needs, and the constraint bounds (2-letter, max 50) are folded in compactly.

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?

For a six-parameter read tool with no output schema and no annotations, the definition is substantially complete: it describes return fields, cost, auth, and the result cap. The unmentioned 'market' parameter and the lack of stage/min_mw value formats are the only meaningful holes.

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 0%, so the description must compensate for all six parameters. It covers five (state with a '2-letter' format hint, county, stage, min_mw, limit with a 'max 50' bound) but entirely omits 'market', and gives no type or value-format guidance for stage or min_mw, leaving a real gap.

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 the resource precisely ('US data center projects from public sources') and enumerates the data carried (MW, stage, power status, utility, opposition, source URLs), which clearly separates it from siblings like dc_deals, dc_legislation, and dc_power. No explicit verb, but the query/list intent is unambiguous.

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?

It lists the available filters (state, county, stage, min_mw, limit), which implies how to narrow results, but it never states when to choose this tool over dc_deals or dc_power, nor any exclusions or prerequisites beyond the API key. Usage is inferable rather than spelled out.

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