Skip to main content
Glama

DC Hub

by cloud.dchub
OverviewDiscussionsAdmin

Get Changes

get_changes
Read-onlyIdempotent

Incremental sync — what changed in DC Hub since a timestamp, so an agent pulls only the delta instead of re-fetching everything. Returns DCPI 7-day market movers, newly discovered facilities, new M&A deals + news — PLUS, for keyed callers with saved sites, a portfolio block answering "did MY sites move?": per-saved-site verdict flips (CAUTION → BUILD), excess-power deltas, alerts fired, and new facilities near each site since your last check. Pass since= or shorthand "24h"/"7d" (default 24h); cache the response generated_at and pass it back next call. Answers "what changed since I last looked", "anything new this week I should know about". Try: get_changes since=7d.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results to return (1-500; default varies by tool)
sinceNoReturn changes since this ISO-8601 timestamp (YYYY-MM-DD or full datetime) or shorthand "24h"/"7d"; default 24h

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. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": {},
+  "description": "DC Hub envelope: tool data fields ride at the top level beside these keys.",
+  "properties": {
+    "_entity": {
+      "description": "Payload class (facility|market|iso_grid|queue_results|deal|report|response); branch on it.",
+      "type": "string"
+    },
+    "_front_door": {
+      "additionalProperties": {},
+      "description": "First-tool hint: plan_query(intent) returns the ordered plan.",
+      "properties": {},
+      "type": "object"
+    },
+    "_return_loop": {
+      "additionalProperties": {},
+      "description": "Next-session delta call (get_changes).",
+      "properties": {},
+      "type": "object"
+    },
+    "citation": {
+      "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."
+    },
+    "provenance": {
+      "additionalProperties": {},
+      "description": "Source, method, as_of, verification_counts, license, cite_as; quote it when citing.",
+      "properties": {},
+      "type": "object"
+    },
+    "quota": {
+      "additionalProperties": {},
+      "description": "Caller quota state (remaining calls, tier).",
+      "properties": {},
+      "type": "object"
+    },
+    "site_evaluation_handoff": {
+      "anyOf": [
+        {
+          "items": {
+            "additionalProperties": {},
+            "properties": {},
+            "type": "object"
+          },
+          "type": "array"
+        },
+        {
+          "additionalProperties": {},
+          "properties": {},
+          "type": "object"
+        }
+      ],
+      "description": "Follow-up calls [{tool, parameters, why}] when the payload carries coordinates."
+    }
+  },
+  "type": "object"
+}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "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": {
-      "anyOf": [
-        {
-          "additionalProperties": {},
-          "properties": {},
-          "type": "object"
-        },
-        {
-          "type": "string"
-        }
-      ],
-      "description": "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."
-    },
-    "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"
-}New value: +null
  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 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"
  5. 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"
+}
  6. 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"
  7. 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"
+}
  8. Changed4 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"Max results to return (1-500; default varies by tool)"
    • changedInput schema / properties / limit / maximum
      Previous value: -9007199254740991New value: +500
    • changedInput schema / properties / limit / minimum
      Previous value: --9007199254740991New value: +1
    • addedInput schema / properties / since / description
      Added value: +"Return changes since this ISO-8601 timestamp (YYYY-MM-DD or full datetime) or shorthand \"24h\"/\"7d\"; default 24h"
  9. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description adds genuine behavioral context beyond them: the caching workflow ('cache the response generated_at and pass it back next call'), the default window, and the keyed-caller-only portfolio block. It doesn't discuss rate limits, pagination, or failure modes, keeping it below 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.

Conciseness3/5

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

Front-loads the core purpose well, but the description is long and partly redundant: the 'what changed since I last looked' phrasing repeats the opening thesis, and the portfolio-block detail is verbose. Several clauses re-explain the same delta idea rather than adding new information.

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 low-complexity, two-optional-parameter tool with rich annotations and an output schema, the description covers everything needed: purpose, format of since, default window, caching pattern, and what the response contains. Nothing an agent needs to select or invoke it correctly is missing.

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 both parameters, including the ISO/shorthand formats and 24h default. The description restates that same format info ('Pass since=<ISO-8601> or shorthand "24h"/"7d"') without adding syntax beyond the schema, so 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+resource and scope: 'Incremental sync — what changed in DC Hub since a timestamp.' It explicitly distinguishes itself from the re-fetch pattern ('pulls only the delta instead of re-fetching everything') and enumerates the payload categories (DCPI movers, new facilities, M&A + news, portfolio block). An agent can tell it apart from list/search siblings without opening the 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?

Gives clear usage contexts — 'what changed since I last looked', 'anything new this week I should know about' — plus a concrete example call (since=7d) and the default (24h). It contrasts with the re-fetch alternative but never names a specific sibling tool that would be preferred for other cases, so it stops short of explicit when-not guidance.

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