Skip to main content
Glama
Sign In

DC Hub

by cloud.dchub
OverviewDiscussionsAdmin

Industry News

get_news
Read-onlyIdempotent

Use this when the user asks for data center industry news or headlines (execute_plan also pulls news inside a broader market question). Curated data center industry news from 40+ trade sources (DCD, Data Center Knowledge, Data Center Frontier, Capacity Media, The Register Data Centre, Fierce Telecom, etc.) refreshed every 30 min. Returns title, summary, source, published_at, and the market/operator entities mentioned. Filter by category (deals/permits/outages/policy/AI). Answers "what is happening in the data center industry this week", "any news on AI capacity". Try: get_news category=AI limit=10. The parameter is category, not topic. Industry news only; do NOT use for structured M&A deal data (use list_transactions) or the construction pipeline (use get_pipeline). limit 1-500 (free 20). Empty data = no matching news: drop category/source or widen date_from/date_to.

Input Schema

NameRequiredDescriptionDefault
limitNoMax results to return (1-500; default varies by tool)
queryNoFree-text keyword to filter news, e.g. "Stargate" or "interconnection queue"
sourceNoRestrict to one trade source, e.g. DCD, "Data Center Frontier", "Capacity Media"
date_toNoLatest published date, ISO-8601 (YYYY-MM-DD)
categoryNoNews topic filter, e.g. deals, permits, outages, policy, AI
date_fromNoEarliest published date, ISO-8601 (YYYY-MM-DD)
min_relevanceNoMinimum relevance score 0-1 to include an item, e.g. 0.5

Output Schema

NameRequiredDescriptionDefault
dataNo
countNo
totalNo
sourceNo
cite_asNo
successNo
articlesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • 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: -{}
  2. Changed32 schema fields changed
    • changedOutput schema / additionalProperties
      Previous value: -{}New value: +true
    • 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 / articles / anyOf
      Removed value: -[
-  {
-    "items": {
-      "additionalProperties": {},
-      "properties": {},
-      "type": "object"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]
    • removedOutput schema / properties / articles / description
      Removed value: -"News rows"
    • 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 / cite_as / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • removedOutput schema / properties / cite_as / description
      Removed value: -"Ready-made attribution line"
    • removedOutput schema / properties / count / anyOf
      Removed value: -[
-  {
-    "anyOf": [
-      {
-        "type": "number"
-      },
-      {
-        "type": "string"
-      }
-    ]
-  },
-  {
-    "type": "null"
-  }
-]
    • removedOutput schema / properties / count / description
      Removed value: -"Rows returned in THIS response"
    • removedOutput schema / properties / data / anyOf
      Removed value: -[
-  {
-    "items": {
-      "additionalProperties": {},
-      "properties": {},
-      "type": "object"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]
    • removedOutput schema / properties / data / description
      Removed value: -"Same rows as `articles`"
    • 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."
    • removedOutput schema / properties / source / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • removedOutput schema / properties / source / description
      Removed value: -"Where the news set comes from"
    • removedOutput schema / properties / success / anyOf
      Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]
    • removedOutput schema / properties / success / description
      Removed value: -"true when the news query succeeded"
    • removedOutput schema / properties / total / anyOf
      Removed value: -[
-  {
-    "anyOf": [
-      {
-        "type": "number"
-      },
-      {
-        "type": "string"
-      }
-    ]
-  },
-  {
-    "type": "null"
-  }
-]
    • removedOutput schema / properties / total / description
      Removed value: -"Total articles matching"
  3. Added
  4. Removed
  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. 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"
  7. 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"
+}
  8. 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"
  9. 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"
+}
  10. Changed9 schema fields changed
    • addedInput schema / properties / category / description
      Added value: +"News topic filter, e.g. deals, permits, outages, policy, AI"
    • addedInput schema / properties / date_from / description
      Added value: +"Earliest published date, ISO-8601 (YYYY-MM-DD)"
    • addedInput schema / properties / date_to / description
      Added value: +"Latest published date, ISO-8601 (YYYY-MM-DD)"
    • 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 / min_relevance / description
      Added value: +"Minimum relevance score 0-1 to include an item, e.g. 0.5"
    • addedInput schema / properties / query / description
      Added value: +"Free-text keyword to filter news, e.g. \"Stargate\" or \"interconnection queue\""
    • addedInput schema / properties / source / description
      Added value: +"Restrict to one trade source, e.g. DCD, \"Data Center Frontier\", \"Capacity Media\""
  11. Changed19 schema fields changed
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • removedInput schema / properties / category / default
      Removed value: -""
    • removedInput schema / properties / category / title
      Removed value: -"Category"
    • removedInput schema / properties / date_from / default
      Removed value: -""
    • removedInput schema / properties / date_from / title
      Removed value: -"Date From"
    • removedInput schema / properties / date_to / default
      Removed value: -""
    • removedInput schema / properties / date_to / title
      Removed value: -"Date To"
    • removedInput schema / properties / limit / default
      Removed value: -20
    • addedInput schema / properties / limit / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / limit / minimum
      Added value: +-9007199254740991
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / properties / min_relevance / default
      Removed value: -0.5
    • removedInput schema / properties / min_relevance / title
      Removed value: -"Min Relevance"
    • removedInput schema / properties / query / default
      Removed value: -""
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • removedInput schema / properties / source / default
      Removed value: -""
    • removedInput schema / properties / source / title
      Removed value: -"Source"
    • removedInput schema / title
      Removed value: -"get_newsArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "get_newsOutput",
-  "type": "object"
-}New value: +null
  12. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "title": "Result",
+      "type": "string"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "get_newsOutput",
+  "type": "object"
+}
  13. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "get_newsOutput",
-  "type": "object"
-}New value: +null
  14. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "title": "Result",
+      "type": "string"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "get_newsOutput",
+  "type": "object"
+}
  15. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "get_newsOutput",
-  "type": "object"
-}New value: +null
  16. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description still adds substantive behaviour: 40+ sources, a 30-minute refresh cadence, the returned field set, the free-tier result cap (20 vs limit 1-500), and remediation for empty results (drop category/source or widen the date range).

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 usage condition, then sourcing, then filters, then a concrete call example and exclusions. It is a dense single block with several query examples that border on redundant, but nearly every sentence carries selection-relevant 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?

An output schema exists so return values need not be explained, yet the description still names the key fields; combined with sourcing, freshness, filter guidance, and sibling exclusions, an agent has everything needed to call it correctly with no required parameters.

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 description coverage is 100%, so the baseline is 3; the description adds value by warning that the filter parameter is named `category`, not `topic`, enumerating accepted categories, and noting the free-tier limit. It still omits how query/source/min_relevance interact (e.g. combining filters), so it is above baseline but not exhaustive.

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?

Specific verb+resource ('Curated data center industry news from 40+ trade sources') with named sources and the exact fields returned (title, summary, source, published_at, entities). It explicitly distinguishes itself from the near-neighbours that could be confused with it: list_transactions for M&A data and get_pipeline for the construction pipeline.

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?

Opens with the trigger condition ('when the user asks for data center industry news or headlines') and names the overlapping sibling execute_plan. It also gives explicit exclusions ('do NOT use for structured M&A deal data... or the construction pipeline') and sample user phrasings, so selection is unambiguous.

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