Skip to main content
Glama

The MW Desk Data Center API

dc_deals

Data center M&A, leasing and financing deals with public price and $/MW where disclosed, with sources. Filters: market, limit (max 50). Costs 3 credits ($0.03) 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_deals"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
stageNo
stateNo
countyNo
marketNo
min_mwNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

With no annotations, the description does real work: it discloses a per-call cost (3 credits / $0.03), an API key requirement, that prices are only present 'where disclosed' (i.e., nullable fields), and a hard cap of 50 on limit. It stops short of describing return shape, pagination, or what 'sources' looks like in the payload.

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 tight sentences: the resource and data attributes come first, then filters, then cost and auth. Every clause carries information and nothing is repeated from structured fields.

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 descriptions, no annotations, and no output schema, the definition is too thin—four filters are undocumented and the return structure is unknown. The cost and API-key notes are helpful but do not close the parameter gap.

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% across six parameters, so the description must compensate and it only documents two: market and limit (adding the useful max-50 bound). The stage, state, county, and min_mw parameters—including their accepted string formats—are completely unexplained anywhere.

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—data center M&A, leasing and financing deals—and states what data it carries (public price, $/MW where disclosed, with sources). That is clearly distinguishable from siblings like dc_power or dc_legislation, though it never explicitly contrasts itself with 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 Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, and no named alternative among dc_projects, dc_pricing, or dc_power is referenced as a routing option. The agent is left to infer that this is the deals dataset from the resource phrase alone.

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