Skip to main content
Glama

DC Hub

by cloud.dchub
OverviewDiscussionsAdmin

Site Selection Canvas

site_selection_canvas
Read-onlyIdempotent

Guided end-to-end 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

TableJSON Schema
NameRequiredDescriptionDefault
isoNoISO/RTO code, e.g. ERCOT or PJM — alias for `region`. Use either; `region` wins if both are sent.
limitNoNumber of shortlist markets to return
stateNoUS state code, e.g. OH — alias for `region`. Use either; `region` wins if both are sent.
regionNoGeography 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_payNoStripe MPP step 1: true returns a signed per-call payment challenge (a quote; no money moves) instead of the free preview. Agents only.
verdictNoOptional 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.
max_monthsNoMaximum acceptable time-to-power in months, 1-120, e.g. 24
capacity_mwNoTarget power load for the build in megawatts (MW), 1-5000, e.g. 100
mpp_credentialNoStripe MPP step 2: the Shared Payment Token minted for challenges[0]; pays that challenge for this one call.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
quotaNoCaller quota state (remaining calls, tier).
_entityNoPayload class (facility|market|iso_grid|queue_results|deal|report|response); branch on it.
citationNoHow to attribute DC Hub: {source, url, license, cite_as, retrieved_at}, or the attribution line as a string.
provenanceNoSource, method, as_of, verification_counts, license, cite_as; quote it when citing.
_front_doorNoFirst-tool hint: plan_query(intent) returns the ordered plan.
_return_loopNoNext-session delta call (get_changes).
site_evaluation_handoffNoFollow-up calls [{tool, parameters, why}] when the payload carries coordinates.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Changed2 schema fields changed
    • 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."
  4. Changed4 schema fields changed
    • 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."
  5. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedOutput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  6. Changed2 schema fields changed
    • 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"
+}
  7. Changed5 schema fields changed
    • 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"
  8. Changed1 schema field changed
    • 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"
+}
  9. Changed5 schema fields changed
    • 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"
  10. Changed1 schema field changed
    • 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"
+}
  11. Changed11 schema fields changed
    • 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"
  12. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: the free vs paid-key tiering ('with a paid key, the synthesis decision layer'), the output contents (DCPI verdict, excess-power headroom, time-to-power, ISO, #1 pick, build sequence, risk flags). It stops short of describing pagination or the empty_result edge (left to schema), so not a 5.

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 purpose, then value, then an example, then exclusions. Dense but every sentence earns its place. The 'find->rank->shortlist->verdict' flow is stated twice, a minor redundancy that keeps it from a 5.

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 9-param, 0-required tool with an output schema and annotations, the description supplies the routing (alternatives), the trigger, and the payoff tiers. Return formatting is properly left to the output schema, and payment mechanics are left to param descriptions. Complete enough for correct invocation.

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 description coverage is 100%, so the schema already documents all 9 parameters including alias precedence and defaults. The description only echoes capacity_mw/region/max_months in an example without adding syntax or semantics. Baseline 3 is appropriate.

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 end-to-end data-center site selection'), describes the pipeline ('one find->rank->shortlist->verdict call over the Data Center Power Index'), and explicitly names the sibling tools it is NOT (analyze_site, get_dchub_recommendation). An agent can distinguish this from the many rank_markets/find_sites siblings without opening a schema.

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 ('give a capacity target + geography + deadline'), explicit exclusions with named alternatives ('Do NOT use for a single known parcel (use analyze_site) or an open-ended question (use get_dchub_recommendation)'), and a concrete invocation example. Both when-to-use and when-not-to-use are covered.

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

All DC Hub toolsInspect
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.

Resources