DC Hub

Site Selection Canvas

site_selection_canvas

Read-onlyIdempotent

Use this when the user wants guided data-center site selection. Give a capacity target + geography + deadline and get a ranked shortlist of US markets (DCPI verdict, excess-power headroom, time-to-power, ISO) — and, with a paid key, the synthesis decision layer: the #1 pick, the why, a build sequence, and risk flags. One find->rank->shortlist->verdict call over the Data Center Power Index. Answers "where should I build 100 MW in Texas by 2028". Try: site_selection_canvas capacity_mw=100 region=TX max_months=24. Do NOT use for a single known parcel (use analyze_site) or an open-ended where-should-I-build question (use get_dchub_recommendation); this runs the full find to rank to shortlist to verdict flow.

Input Schema

Name	Required	Description
`iso`	No	ISO/RTO code, e.g. ERCOT or PJM — alias for `region`. Use either; `region` wins if both are sent.
`limit`	No	Number of shortlist markets to return
`state`	No	US state code, e.g. OH — alias for `region`. Use either; `region` wins if both are sent.
`region`	No	Geography scope: a US state code like TX, an ISO like ERCOT, or a region like us/apac. `state` and `iso` are accepted as aliases for this same filter.
`mpp_pay`	No	Per-call payment quote (Stripe MPP): true returns a signed payment challenge instead of the free preview; no money moves. Set it only after your human has explicitly approved paying for this call.
`verdict`	No	Optional DCPI verdict filter: BUILD, CAUTION, or AVOID — or ALL to see every scored market in the geography. Defaults to BUILD,CAUTION, so a geography whose markets are all AVOID returns matched:0 plus an `empty_result` block explaining…
`max_months`	No	Maximum acceptable time-to-power in months, 1-120, e.g. 24
`capacity_mw`	No	Target power load for the build in megawatts (MW), 1-5000, e.g. 100
`mpp_credential`	No	Per-call payment (Stripe MPP): the Shared Payment Token for challenges[0]; pays that challenge for this one call. Send it only with your human's explicit approval of the charge.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 22, 2026

addedInput schema / properties / mpp_credential

Added value: +{
+  "description": "Per-call payment (Stripe MPP): the Shared Payment Token for challenges[0]; pays that challenge for this one call. Send it only with your human's explicit approval of the charge.",
+  "type": "string"
+}

addedInput schema / properties / mpp_pay

Added value: +{
+  "description": "Per-call payment quote (Stripe MPP): true returns a signed payment challenge instead of the free preview; no money moves. Set it only after your human has explicitly approved paying for this call.",
+  "type": "boolean"
+}

Changed2 schema fields changedOct 22, 2026

removedInput schema / properties / mpp_credential

Removed value: -{
-  "description": "Per-call payment (Stripe MPP): the Shared Payment Token for challenges[0]; pays that challenge for this one call. Send it only with your human's explicit approval of the charge.",
-  "type": "string"
-}

removedInput schema / properties / mpp_pay

Removed value: -{
-  "description": "Per-call payment quote (Stripe MPP): true returns a signed payment challenge instead of the free preview; no money moves. Set it only after your human has explicitly approved paying for this call.",
-  "type": "boolean"
-}

Changed2 schema fields changedOct 20, 2026

changedInput schema / properties / mpp_credential / description

Previous value: -"Stripe MPP step 2: the Shared Payment Token minted for challenges[0]; pays that challenge for this one call."New value: +"Per-call payment (Stripe MPP): the Shared Payment Token for challenges[0]; pays that challenge for this one call. Send it only with your human's explicit approval of the charge."

changedInput schema / properties / mpp_pay / description

Previous value: -"Stripe MPP step 1: true returns a signed per-call payment challenge (a quote; no money moves) instead of the free preview. Agents only."New value: +"Per-call payment quote (Stripe MPP): true returns a signed payment challenge instead of the free preview; no money moves. Set it only after your human has explicitly approved paying for this call."

Changed7 schema fields changedOct 19, 2026
- removedOutput schema / properties / _entity
```
Removed value: -{
-  "type": "string"
-}
```
- removedOutput schema / properties / _front_door
```
Removed value: -{
-  "type": "object"
-}
```
- removedOutput schema / properties / _return_loop
```
Removed value: -{
-  "type": "object"
-}
```
- removedOutput schema / properties / citation
```
Removed value: -{}
```
- removedOutput schema / properties / provenance
```
Removed value: -{
-  "type": "object"
-}
```
- removedOutput schema / properties / quota
```
Removed value: -{
-  "type": "object"
-}
```
- removedOutput schema / properties / site_evaluation_handoff
```
Removed value: -{}
```

Changed20 schema fields changedOct 18, 2026

changedInput schema / properties / verdict / description

Previous value: -"Optional DCPI verdict filter: BUILD, CAUTION, or AVOID — or ALL to see every scored market in the geography. Defaults to BUILD,CAUTION, so a geography whose markets are all AVOID returns matched:0 plus an `empty_result` block explaining that; re-run with verdict=ALL to see those rows."New value: +"Optional DCPI verdict filter: BUILD, CAUTION, or AVOID — or ALL to see every scored market in the geography. Defaults to BUILD,CAUTION, so a geography whose markets are all AVOID returns matched:0 plus an `empty_result` block explaining…"

changedOutput schema / additionalProperties
```
Previous value: -{}New value: +true
```

removedOutput schema / description

Removed value: -"DC Hub envelope: tool data fields ride at the top level beside these keys."

removedOutput schema / properties / _entity / description

Removed value: -"Payload class (facility|market|iso_grid|queue_results|deal|report|response); branch on it."

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

removedOutput schema / properties / _front_door / description

Removed value: -"First-tool hint: plan_query(intent) returns the ordered plan."

removedOutput schema / properties / _front_door / properties
```
Removed value: -{}
```
removedOutput schema / properties / _return_loop / additionalProperties
```
Removed value: -{}
```
removedOutput schema / properties / _return_loop / description
```
Removed value: -"Next-session delta call (get_changes)."
```
removedOutput schema / properties / _return_loop / properties
```
Removed value: -{}
```

removedOutput schema / properties / citation / anyOf

Removed value: -[
-  {
-    "additionalProperties": {},
-    "properties": {},
-    "type": "object"
-  },
-  {
-    "type": "string"
-  }
-]

removedOutput schema / properties / citation / description

Removed value: -"How to attribute DC Hub: {source, url, license, cite_as, retrieved_at}, or the attribution line as a string."

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

removedOutput schema / properties / provenance / description

Removed value: -"Source, method, as_of, verification_counts, license, cite_as; quote it when citing."

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

removedOutput schema / properties / quota / description

Removed value: -"Caller quota state (remaining calls, tier)."

removedOutput schema / properties / quota / properties
```
Removed value: -{}
```

removedOutput schema / properties / site_evaluation_handoff / anyOf

Removed value: -[
-  {
-    "items": {
-      "additionalProperties": {},
-      "properties": {},
-      "type": "object"
-    },
-    "type": "array"
-  },
-  {
-    "additionalProperties": {},
-    "properties": {},
-    "type": "object"
-  }
-]

removedOutput schema / properties / site_evaluation_handoff / description

Removed value: -"Follow-up calls [{tool, parameters, why}] when the payload carries coordinates."

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."

Changed4 schema fields changedAug 29, 2026

addedInput schema / properties / iso

Added value: +{
+  "description": "ISO/RTO code, e.g. ERCOT or PJM — alias for `region`. Use either; `region` wins if both are sent.",
+  "type": "string"
+}

changedInput schema / properties / region / description

Previous value: -"Geography scope, e.g. a US state code like TX or a region like us/apac"New value: +"Geography scope: a US state code like TX, an ISO like ERCOT, or a region like us/apac. `state` and `iso` are accepted as aliases for this same filter."

addedInput schema / properties / state

Added value: +{
+  "description": "US state code, e.g. OH — alias for `region`. Use either; `region` wins if both are sent.",
+  "type": "string"
+}

changedInput schema / properties / verdict / description

Previous value: -"Optional DCPI verdict filter: BUILD, CAUTION, or AVOID"New value: +"Optional DCPI verdict filter: BUILD, CAUTION, or AVOID — or ALL to see every scored market in the geography. Defaults to BUILD,CAUTION, so a geography whose markets are all AVOID returns matched:0 plus an `empty_result` block explaining that; re-run with verdict=ALL to see those rows."

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#"

Changed2 schema fields changedAug 17, 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"
+}

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"
+}

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"
+}

Changed11 schema fields changedJul 2, 2026

addedInput schema / properties / capacity_mw / description

Added value: +"Target power load for the build in megawatts (MW), 1-5000, e.g. 100"

changedInput schema / properties / capacity_mw / maximum
```
Previous value: -9007199254740991New value: +5000
```
changedInput schema / properties / capacity_mw / minimum
```
Previous value: --9007199254740991New value: +1
```

addedInput schema / properties / limit / description

Added value: +"Number of shortlist markets to return"

changedInput schema / properties / limit / maximum

Previous value: -9007199254740991New value: +500

changedInput schema / properties / limit / minimum

Previous value: --9007199254740991New value: +1

addedInput schema / properties / max_months / description

Added value: +"Maximum acceptable time-to-power in months, 1-120, e.g. 24"

changedInput schema / properties / max_months / maximum
```
Previous value: -9007199254740991New value: +120
```
changedInput schema / properties / max_months / minimum
```
Previous value: --9007199254740991New value: +1
```

addedInput schema / properties / region / description

Added value: +"Geography scope, e.g. a US state code like TX or a region like us/apac"

addedInput schema / properties / verdict / description

Added value: +"Optional DCPI verdict filter: BUILD, CAUTION, or AVOID"

AddedJun 3, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds genuinely useful tiering context (free preview vs paid-key synthesis layer with #1 pick, why, build sequence, risk flags) and the end-to-end flow, but payment mechanics themselves live in the schema rather than the description, so this is incremental rather than rich.

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?

Front-loaded with the use case, then outputs, then an example, then the do-not-use routing. Slightly dense with parentheticals and an em-dash-heavy sentence, but each clause carries distinct information and nothing is redundant.

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

Completeness5/5

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

For a nine-parameter tool with an output schema and full annotation coverage, the description covers the trigger, the pipeline, the output surface, the paid tier, and the sibling routing. An agent has everything needed to select and invoke it correctly.

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 100%, so all nine parameters are already documented with aliasing rules (region vs state/iso) and ranges. The description's sample invocation (capacity_mw=100 region=TX max_months=24) illustrates typical values but adds no semantics beyond what the schema states. Baseline 3 applies.

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 and resource — guided data-center site selection over the Data Center Power Index — and names the exact pipeline (find->rank->shortlist->verdict) plus the concrete outputs (DCPI verdict, excess-power headroom, time-to-power, ISO). It explicitly distinguishes itself from siblings analyze_site and get_dchub_recommendation.

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

Usage Guidelines5/5

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

Gives the trigger condition (user wants guided site selection with a capacity target + geography + deadline) and two explicit exclusions with named alternatives: single known parcel -> analyze_site, open-ended question -> get_dchub_recommendation. The sample call further anchors when it applies.

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.