Skip to main content
Glama
Sign In
azmartone67

DC Hub: Data Center, Power Grid & Energy Intelligence

by azmartone67
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
JavaScript
Remote

Compare Sites

compare_sites
Read-onlyIdempotent

Compare 2-4 candidate data center sites side by side to select a suitable location for a given power capacity. Returns site scores and a recommended winner with reasoning.

Instructions

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

NameRequiredDescriptionDefault
sitesNoAlternative to locations: an array of {lat, lon} (or {lat, lng}) objects, 2-4 sites
locationsNoSemicolon-separated list of 2-4 "lat,lon" pairs to compare, e.g. "33.45,-112.07;39.04,-77.48"
capacity_mwNoTarget power load for the build in megawatts (MW), e.g. 50 (typical 50-500)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv2.12.45
    • 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
      Removed value: -{
-  "description": "Payload class (facility|market|iso_grid|queue_results|deal|report|response); branch on it.",
-  "type": "string"
-}
    • removedOutput schema / properties / _front_door
      Removed value: -{
-  "additionalProperties": {},
-  "description": "First-tool hint: plan_query(intent) returns the ordered plan.",
-  "properties": {},
-  "type": "object"
-}
    • removedOutput schema / properties / _return_loop
      Removed value: -{
-  "additionalProperties": {},
-  "description": "Next-session delta call (get_changes).",
-  "properties": {},
-  "type": "object"
-}
    • removedOutput schema / properties / citation
      Removed value: -{
-  "anyOf": [
-    {
-      "additionalProperties": {},
-      "properties": {},
-      "type": "object"
-    },
-    {
-      "type": "string"
-    }
-  ],
-  "description": "How to attribute DC Hub: {source, url, license, cite_as, retrieved_at}, or the attribution line as a string."
-}
    • removedOutput schema / properties / provenance
      Removed value: -{
-  "additionalProperties": {},
-  "description": "Source, method, as_of, verification_counts, license, cite_as; quote it when citing.",
-  "properties": {},
-  "type": "object"
-}
    • removedOutput schema / properties / quota
      Removed value: -{
-  "additionalProperties": {},
-  "description": "Caller quota state (remaining calls, tier).",
-  "properties": {},
-  "type": "object"
-}
    • removedOutput schema / properties / site_evaluation_handoff
      Removed value: -{
-  "anyOf": [
-    {
-      "items": {
-        "additionalProperties": {},
-        "properties": {},
-        "type": "object"
-      },
-      "type": "array"
-    },
-    {
-      "additionalProperties": {},
-      "properties": {},
-      "type": "object"
-    }
-  ],
-  "description": "Follow-up calls [{tool, parameters, why}] when the payload carries coordinates."
-}
  2. Changed8 schema fields changedv2.12.43
    • changedOutput schema / description
      Previous value: -"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."New value: +"DC Hub envelope: tool data fields ride at the top level beside these keys."
    • changedOutput schema / properties / _entity / description
      Previous value: -"Payload class discriminator (e.g. facility|market|iso_grid|queue_results|deal|report|response) — branch on this before parsing the rest."New value: +"Payload class (facility|market|iso_grid|queue_results|deal|report|response); branch on it."
    • changedOutput schema / properties / _front_door / description
      Previous value: -"In-band front-door hint (first workflow-entry tool of a session): call plan_query(intent) first for the ordered multi-step plan."New value: +"First-tool hint: plan_query(intent) returns the ordered plan."
    • changedOutput schema / properties / _return_loop / description
      Previous value: -"Suggested next-session delta call (get_changes since=24h) so you pull only what changed."New value: +"Next-session delta call (get_changes)."
    • changedOutput schema / properties / citation / description
      Previous 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."New value: +"How to attribute DC Hub: {source, url, license, cite_as, retrieved_at}, or the attribution line as a string."
    • changedOutput schema / properties / provenance / description
      Previous value: -"Collection-level provenance block: {source, method, as_of, verification_counts, cite_url_template, license, cite_as}. Quote the verification level when citing."New value: +"Source, method, as_of, verification_counts, license, cite_as; quote it when citing."
    • changedOutput schema / properties / quota / description
      Previous value: -"Caller quota state (remaining calls, tier) when available."New value: +"Caller quota state (remaining calls, tier)."
    • changedOutput schema / properties / site_evaluation_handoff / description
      Previous value: -"Pre-built follow-up calls (analyze_site / get_water_risk args) when the payload carries coordinates — an array of {tool, parameters, why} entries."New value: +"Follow-up calls [{tool, parameters, why}] when the payload carries coordinates."
  3. 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#"
  4. Changed5 schema fields changedv2.3.20
    • 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"
  5. Changed2 schema fields changedv2.3.12
    • addedInput schema / properties / sites
      Added value: +{
+  "description": "Alternative to locations: an array of {lat, lon} (or {lat, lng}) objects, 2-4 sites"
+}
    • 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"
+    },
+    "_front_door": {
+      "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"
+    },
+    "_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": {
+      "anyOf": [
+        {
+          "items": {
+            "additionalProperties": {},
+            "properties": {},
+            "type": "object"
+          },
+          "type": "array"
+        },
+        {
+          "additionalProperties": {},
+          "properties": {},
+          "type": "object"
+        }
+      ],
+      "description": "Pre-built follow-up calls (analyze_site / get_water_risk args) when the payload carries coordinates — an array of {tool, parameters, why} entries."
+    }
+  },
+  "type": "object"
+}
  6. Changed1 schema field changedv2.3.7
    • 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"
+}
  7. Changed1 schema field changedv2.3.6
    • 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\""
  8. First observedv2.1.19

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, closed-world), and the description adds the non-obvious behavioral layer: tiered data availability (keyless = bands only, free key = names/counts, paid plan = figures and the pick). That gating materially changes what the agent can promise a user and is not inferable from structured fields.

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?

Front-loaded with the trigger condition, then format, then return tiers, then an example – each sentence carries distinct information with no filler or repetition.

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?

An output schema exists so return-shape detail is unnecessary, yet the description still supplies the crucial tier-dependency of results and the recommendation behavior. Nothing an agent needs to decide whether and how to call this is missing.

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 coverage is 100%, so the string format and capacity_mw semantics are already documented. The description adds value by restating the accepted 'lat,lon;lat,lon' form in context and framing capacity_mw as optional and tied to the user's build, but it does not explain the sites[] alternative or the 2-4 bound enforcement beyond what the schema says.

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_sites', sites side by side) and scopes it precisely: 2-4 candidate sites, returns analyze_site scores plus a recommended winner. An agent can tell it apart from single-site siblings like analyze_site or rank_sites 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?

Explicit trigger ('when the user has 2-4 candidate sites and asks which is best') plus an example utterance ('Phoenix vs Ashburn for 50 MW?'). It also spells out the fallback path when the caller lacks a key, so an agent knows what it will actually get before calling.

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

Deploy Server

Other Tools