DC Hub

Rank Markets

rank_markets

Read-onlyIdempotent

Use this whenever the user asks where a data center can get grid power, how fast, or whether a market is a BUILD, CAUTION or AVOID (e.g. "Where can a 100 MW data center get power fastest?"): DCPI scores 300+ markets daily on Excess Power and Grid Constraint, CC BY 4.0. For a ranked list on power questions, call with criteria="ai_ready". Call when the user wants a ranked list of data-center markets: top N by cheapest_power, most_capacity, most_operators, fastest_growing, best_overall, or ai_ready (where new AI load can land, per DCPI). Filter by region, min_capacity_mw. Returns ranked rows with score, MW and a slug for follow-ups; score is the sort value, not a 0-100 scale, and score_basis says what it is (ai_ready omits it and explains its composite in methodology). Keyless: a trimmed preview; a free key gets a few full lists a day. Ex: "Top 10 US markets, ai_ready." Returns market slugs to feed get_market_intel and get_market_dcpi_rank. limit 1-500; set projection=identity_only to save tokens.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Number of markets to return, 1-50 (default 10)
`fields`	No	Return ONLY these row fields (array or comma string) — a token diet. The response envelope (citation, provenance, as_of, coverage, request_interpretation, the human relay line) is NEVER projected away; a projection narrows ROWS only.
`region`	No	Region scope: "global", "us" (default), "canada", "eu", "apac", or "americas"
`mpp_pay`	No	Stripe MPP step 1: true returns a signed per-call payment challenge (a quote; no money moves) instead of the free preview. Agents only.
`criteria`	No	Ranking criterion: "cheapest_power", "most_capacity", "most_operators", "fastest_growing", "best_overall" (default), or "ai_ready" (DCPI buildability — where new AI load can land, for AI-campus siting; region us/global)
`projection`	No	Named field preset, cheaper to send than a field list: market_summary (ranking rows), siting_summary (site/point rows), identity_only (ids + names).
`mpp_credential`	No	Stripe MPP step 2: the Shared Payment Token minted for challenges[0]; pays that challenge for this one call.
`min_capacity_mw`	No	Minimum existing capacity filter in megawatts (MW), e.g. 100

Output Schema

TableJSON Schema

Name	Required	Description
`tier`	No	Tier the response was served at
`quota`	No	Caller quota state (remaining calls, tier).
`region`	No	Region filter applied
`_entity`	No	Payload class (facility\|market\|iso_grid\|queue_results\|deal\|report\|response); branch on it.
`cite_as`	No	Ready-made attribution line
`results`	No	Ranked markets
`citation`	No	How to attribute DC Hub: {source, url, license, cite_as, retrieved_at}, or the attribution line as a string.
`criteria`	No	Ranking criterion used
`provenance`	No	Source, method, as_of, verification_counts, license, cite_as; quote it when citing.
`_front_door`	No	First-tool hint: plan_query(intent) returns the ordered plan.
`data_source`	No	Where the data comes from
`methodology`	No	Method note
`score_basis`	No	How the score is computed
`_return_loop`	No	Next-session delta call (get_changes).
`result_count`	No	Rows returned in THIS response
`site_evaluation_handoff`	No	Follow-up calls [{tool, parameters, why}] when the payload carries coordinates.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 9, 2026
RemovedSep 29, 2026

Changed2 schema fields changedSep 29, 2026

changedInput schema / properties / mpp_credential / description

Previous value: -"Autonomous payment (Stripe MPP), step 2: the Shared Payment Token you minted for challenges[0]. Set it here to pay $0.50 for this single call and receive the full result — no API key, no subscription, no human. One payment covers one call."New value: +"Autonomous payment (Stripe MPP), step 2: the Shared Payment Token you minted for challenges[0]. Set it here to pay that challenge for this single call and receive the full result — no API key, no subscription, no human. One payment covers one call."

changedInput schema / properties / mpp_pay / description

Previous value: -"Autonomous payment (Stripe MPP), step 1: set true to receive a signed $0.50 payment challenge for this call instead of the free preview. No money moves — a challenge is a price quote. Humans never set this, so it does not affect the normal free/trial funnel."New value: +"Autonomous payment (Stripe MPP), step 1: set true to receive a signed per-call payment challenge (the challenge states the amount) for this call instead of the free preview. No money moves — a challenge is a price quote. Humans never set this, so it does not affect the normal free/trial funnel."

Changed2 schema fields changedSep 8, 2026

addedInput schema / properties / mpp_credential

Added value: +{
+  "description": "Autonomous payment (Stripe MPP), step 2: the Shared Payment Token you minted for challenges[0]. Set it here to pay $0.50 for this single call and receive the full result — no API key, no subscription, no human. One payment covers one call.",
+  "type": "string"
+}

addedInput schema / properties / mpp_pay

Added value: +{
+  "description": "Autonomous payment (Stripe MPP), step 1: set true to receive a signed $0.50 payment challenge for this call instead of the free preview. No money moves — a challenge is a price quote. Humans never set this, so it does not affect the normal free/trial funnel.",
+  "type": "boolean"
+}

Changed2 schema fields changedAug 29, 2026

addedInput schema / properties / fields

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "string"
+    }
+  ],
+  "description": "Return ONLY these row fields (array or comma string) — a token diet. The response envelope (citation, provenance, as_of, coverage, request_interpretation, the human relay line) is NEVER projected away; a projection narrows ROWS only."
+}

addedInput schema / properties / projection

Added value: +{
+  "description": "Named field preset, cheaper to send than a field list: market_summary (ranking rows), siting_summary (site/point rows), identity_only (ids + names).",
+  "enum": [
+    "siting_summary",
+    "market_summary",
+    "identity_only"
+  ],
+  "type": "string"
+}

Changed2 schema fields changedAug 21, 2026

removedInput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

removedOutput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

Changed5 schema fields changedAug 11, 2026

removedOutput schema / properties / citation / additionalProperties
```
Removed value: -{}
```

addedOutput schema / properties / citation / anyOf

Added value: +[
+  {
+    "additionalProperties": {},
+    "properties": {},
+    "type": "object"
+  },
+  {
+    "type": "string"
+  }
+]

changedOutput schema / properties / citation / description

Previous value: -"Machine-readable citation: how to attribute DC Hub (dchub.cloud) for this payload."New value: +"Machine-readable citation: how to attribute DC Hub (dchub.cloud) for this payload. Normally an OBJECT {source, url, license, cite_as, retrieved_at}; a bare string is accepted and carries the attribution line itself."

removedOutput schema / properties / citation / properties
```
Removed value: -{}
```
removedOutput schema / properties / citation / type
```
Removed value: -"object"
```

Changed1 schema field changedJul 21, 2026

addedOutput schema / properties / _front_door

Added value: +{
+  "additionalProperties": {},
+  "description": "In-band front-door hint (first workflow-entry tool of a session): call plan_query(intent) first for the ordered multi-step plan.",
+  "properties": {},
+  "type": "object"
+}

Changed1 schema field changedJul 20, 2026

changedInput schema / properties / criteria / description

Previous value: -"Ranking criterion: \"cheapest_power\", \"most_capacity\", \"most_operators\", \"fastest_growing\", or \"best_overall\" (default)"New value: +"Ranking criterion: \"cheapest_power\", \"most_capacity\", \"most_operators\", \"fastest_growing\", \"best_overall\" (default), or \"ai_ready\" (DCPI buildability — where new AI load can land, for AI-campus siting; region us/global)"

Changed5 schema fields changedJul 18, 2026

removedOutput schema / properties / site_evaluation_handoff / additionalProperties
```
Removed value: -{}
```

addedOutput schema / properties / site_evaluation_handoff / anyOf

Added value: +[
+  {
+    "items": {
+      "additionalProperties": {},
+      "properties": {},
+      "type": "object"
+    },
+    "type": "array"
+  },
+  {
+    "additionalProperties": {},
+    "properties": {},
+    "type": "object"
+  }
+]

changedOutput schema / properties / site_evaluation_handoff / description

Previous value: -"Pre-built follow-up call (analyze_site / get_water_risk args) when the payload carries coordinates."New value: +"Pre-built follow-up calls (analyze_site / get_water_risk args) when the payload carries coordinates — an array of {tool, parameters, why} entries."

removedOutput schema / properties / site_evaluation_handoff / properties
```
Removed value: -{}
```
removedOutput schema / properties / site_evaluation_handoff / type
```
Removed value: -"object"
```

Changed1 schema field changedJul 17, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "description": "DC Hub envelope: structuredContent mirrors the JSON payload in content[0].text — tool-specific data fields ride at the top level alongside these envelope keys.",
+  "properties": {
+    "_entity": {
+      "description": "Payload class discriminator (e.g. facility|market|iso_grid|queue_results|deal|report|response) — branch on this before parsing the rest.",
+      "type": "string"
+    },
+    "_return_loop": {
+      "additionalProperties": {},
+      "description": "Suggested next-session delta call (get_changes since=24h) so you pull only what changed.",
+      "properties": {},
+      "type": "object"
+    },
+    "citation": {
+      "additionalProperties": {},
+      "description": "Machine-readable citation: how to attribute DC Hub (dchub.cloud) for this payload.",
+      "properties": {},
+      "type": "object"
+    },
+    "provenance": {
+      "additionalProperties": {},
+      "description": "Collection-level provenance block: {source, method, as_of, verification_counts, cite_url_template, license, cite_as}. Quote the verification level when citing.",
+      "properties": {},
+      "type": "object"
+    },
+    "quota": {
+      "additionalProperties": {},
+      "description": "Caller quota state (remaining calls, tier) when available.",
+      "properties": {},
+      "type": "object"
+    },
+    "site_evaluation_handoff": {
+      "additionalProperties": {},
+      "description": "Pre-built follow-up call (analyze_site / get_water_risk args) when the payload carries coordinates.",
+      "properties": {},
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

Changed6 schema fields changedJul 2, 2026

addedInput schema / properties / criteria / description

Added value: +"Ranking criterion: \"cheapest_power\", \"most_capacity\", \"most_operators\", \"fastest_growing\", or \"best_overall\" (default)"

addedInput schema / properties / limit / description

Added value: +"Number of markets to return, 1-50 (default 10)"

changedInput schema / properties / limit / maximum

Previous value: -9007199254740991New value: +500

changedInput schema / properties / limit / minimum

Previous value: --9007199254740991New value: +1

addedInput schema / properties / min_capacity_mw / description

Added value: +"Minimum existing capacity filter in megawatts (MW), e.g. 100"

addedInput schema / properties / region / description

Added value: +"Region scope: \"global\", \"us\" (default), \"canada\", \"eu\", \"apac\", or \"americas\""

AddedMay 24, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful undisclosed behavior: the keyless tier returns only a trimmed preview, a free key buys a few full lists per day, and score is a sort value rather than a 0-100 normalization with score_basis explaining its meaning. That materially changes how an agent interprets results.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The trigger condition is front-loaded, which is right, but the body is a dense run-on mixing use cases, criteria enumeration, return semantics, auth tiers and an example, with some repetition between the opening sentence and "Call when the user wants a ranked list...". It is informative but could be trimmed and split into scannable lines.

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 an 8-parameter tool with an output schema, the description covers what matters operationally: when to call, which criteria, region/filter usage, the keyless-vs-key access model, and follow-up tools for the returned slugs. Return-value detail is largely delegated to the output schema, which is appropriate.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3; the description goes beyond it by explaining which criteria to pick for power questions (ai_ready), that projection=identity_only saves tokens, and that region/min_capacity_mw are filters. It also restates the limit range (1-500) consistent with the schema bounds, adding usable range guidance.

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

Purpose5/5

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

States a specific verb (rank) and resource (markets) and immediately frames the outcome categories it produces (BUILD, CAUTION, AVOID) plus the criteria vocabulary. It also distinguishes itself from siblings by naming get_market_intel and get_market_dcpi_rank as follow-up consumers of the returned slugs, so an agent can separate this ranking tool from the per-market lookup tools.

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

Usage Guidelines4/5

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

Gives concrete trigger conditions ("whenever the user asks where a data center can get grid power, how fast, or whether a market is BUILD/CAUTION/AVOID") and a worked example with the recommended criteria="ai_ready". It does not, however, explicitly say when NOT to use it versus the many sibling market tools (get_market_context, get_market_dcpi_rank, ai_capacity_index), leaving that to inference.

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

All DC Hub tools Inspect

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.