DC Hub

Compare Sites

compare_sites

Read-onlyIdempotent

Use this when the user has 2-4 candidate data center sites and asks which is best. Pass locations as "lat,lon;lat,lon" and optional capacity_mw. Returns each site's analyze_site scores side by side plus a recommended winner and why. Keyless returns each site's verdict band and power band, with the other factors named; a free key adds names and counts without figures; scores and figures need a paid DC Hub plan, as does the pick. Ex: "Phoenix vs Ashburn for 50 MW?"

Input Schema

Name	Required	Description
`sites`	No	Alternative to locations: an array of {lat, lon} (or {lat, lng}) objects, 2-4 sites
`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.
`locations`	No	Semicolon-separated list of 2-4 "lat,lon" pairs to compare, e.g. "33.45,-112.07;39.04,-77.48"
`capacity_mw`	No	Target power load for the build in megawatts (MW), e.g. 50 (typical 50-500)
`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: -{}
```

Changed19 schema fields changedOct 18, 2026

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

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

Changed1 schema field changedJul 16, 2026

addedInput schema / properties / sites

Added value: +{
+  "description": "Alternative to locations: an array of {lat, lon} (or {lat, lng}) objects, 2-4 sites"
+}

Changed1 schema field changedJul 4, 2026

addedInput schema / properties / capacity_mw

Added value: +{
+  "description": "Target power load for the build in megawatts (MW), e.g. 50 (typical 50-500)",
+  "type": "number"
+}

Changed1 schema field changedJul 2, 2026

addedInput schema / properties / locations / description

Added value: +"Semicolon-separated list of 2-4 \"lat,lon\" pairs to compare, e.g. \"33.45,-112.07;39.04,-77.48\""

Changed5 schema fields changedApr 29, 2026

addedInput schema / $schema

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

removedInput schema / properties / locations / default
```
Removed value: -""
```
removedInput schema / properties / locations / title
```
Removed value: -"Locations"
```

removedInput schema / title

Removed value: -"compare_sitesArguments"

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "compare_sitesOutput",
-  "type": "object"
-}New value: +null

Changed1 schema field changedApr 18, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "title": "Result",
+      "type": "string"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "compare_sitesOutput",
+  "type": "object"
+}

Changed1 schema field changedApr 11, 2026

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "compare_sitesOutput",
-  "type": "object"
-}New value: +null

Changed1 schema field changedMar 31, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "title": "Result",
+      "type": "string"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "compare_sitesOutput",
+  "type": "object"
+}

Changed1 schema field changedMar 26, 2026

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "compare_sitesOutput",
-  "type": "object"
-}New value: +null

AddedMar 20, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations only cover safety (readOnly/idempotent/non-destructive), yet the description discloses the entire tiered output contract — keyless returns only verdict and power bands, a free key adds names/counts without figures, and scores plus the winner require a paid plan. It also frames the payment path (mpp_pay returning a signed challenge rather than moving money), which is far beyond what structured fields convey.

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?

Four dense sentences that lead with the trigger and the input format, then the return contract, then the example. Every sentence carries information, though the tier explanation is compressed enough to need a careful read.

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?

Covers trigger, input format, capacity hint, tier-gated return content and payment behavior; with an output schema present it need not enumerate return fields. An agent has everything needed to select and invoke this 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 description coverage is 100%, so locations format, {lat,lon} alternatives, capacity_mw range and the MPP payment parameters are already fully documented. The description restates the locations string format and 'optional capacity_mw' but adds no syntax or semantics the schema lacks, so it sits at the baseline.

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 ('compare' 2-4 candidate sites, returns side-by-side analyze_site scores plus a winner) and gives the exact user situation that triggers it. An agent can distinguish this from analyze_site (single site) and rank_sites (ranking) without opening any schema.

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?

Explicit trigger condition: the user has 2-4 candidates and asks which is best, plus a concrete example ('Phoenix vs Ashburn for 50 MW?'). It implies but never names the alternative single-site tool or when to use rank_sites instead, so routing is clear but not fully exclusive.

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.

Compare Sites

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources