DC Hub

Industry News

get_news

Read-onlyIdempotent

FRONT DOOR CHECK — if news is only ONE input to a bigger question (is this market heating up, should we still build here), call execute_plan(intent="<the user's question, unchanged>") and let it pull news alongside the market and grid reads. If the user actually wants the headlines, get_news IS the right call — one round trip; do not send a plain news request through the planner. 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

TableJSON Schema

Name	Required	Description
`limit`	No	Max results to return (1-500; default varies by tool)
`query`	No	Free-text keyword to filter news, e.g. "Stargate" or "interconnection queue"
`source`	No	Restrict to one trade source, e.g. DCD, "Data Center Frontier", "Capacity Media"
`date_to`	No	Latest published date, ISO-8601 (YYYY-MM-DD)
`category`	No	News topic filter, e.g. deals, permits, outages, policy, AI
`date_from`	No	Earliest published date, ISO-8601 (YYYY-MM-DD)
`min_relevance`	No	Minimum relevance score 0-1 to include an item, e.g. 0.5

Output Schema

TableJSON Schema

Name	Required	Description
`data`	No	Same rows as `articles`
`count`	No	Rows returned in THIS response
`quota`	No	Caller quota state (remaining calls, tier).
`total`	No	Total articles matching
`source`	No	Where the news set comes from
`_entity`	No	Payload class (facility\|market\|iso_grid\|queue_results\|deal\|report\|response); branch on it.
`cite_as`	No	Ready-made attribution line
`success`	No	true when the news query succeeded
`articles`	No	News rows
`citation`	No	How to attribute DC Hub: {source, url, license, cite_as, retrieved_at}, or the attribution line as a string.
`provenance`	No	Source, method, as_of, verification_counts, license, cite_as; quote it when citing.
`_front_door`	No	First-tool hint: plan_query(intent) returns the ordered plan.
`_return_loop`	No	Next-session delta call (get_changes).
`site_evaluation_handoff`	No	Follow-up calls [{tool, parameters, why}] when the payload carries coordinates.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 9, 2026
RemovedSep 29, 2026

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

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

Changed9 schema fields changedJul 2, 2026

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

Changed19 schema fields changedApr 29, 2026
- 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
```

Changed1 schema field changedApr 18, 2026

changedOutput schema / (root)

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

Changed1 schema field changedApr 11, 2026

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "get_newsOutput",
-  "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": "get_newsOutput",
+  "type": "object"
+}

Changed1 schema field changedMar 26, 2026

changedOutput schema / (root)

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

First observedMar 6, 2026

TDQS

A4.6/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), so the description adds genuinely new behavior: 30-minute refresh cadence, source breadth, the 'free 20' limit tier implying paid quota, and what an empty result means plus how to remediate it. It does not discuss auth requirements or latency, which is a minor residual gap rather than a failure.

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 highest-stakes decision (whether to call this tool at all), and most sentences carry routing, scope, or recovery information. It is dense rather than bloated, though the trailing 'Try: get_news category=AI limit=10' and the return-field list add some redundancy given the schema and output schema already exist.

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 read-only, zero-required-parameter filter tool with an output schema, the description covers routing, scope boundaries, filter semantics, quota, and empty-result recovery. Nothing an agent needs in order to select and invoke it correctly 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 baseline would be 3. The description exceeds that by flagging a common mistake ('The parameter is `category`, not `topic`'), giving a concrete call example, restating the limit range with the free-tier cutoff, and prescribing filter-widening when results are empty.

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 resource ('Curated data center industry news from 40+ trade sources' with named outlets) and what it returns (title, summary, source, published_at, entities). It explicitly separates itself from siblings, telling the agent not to use it for structured M&A data (list_transactions) or the construction pipeline (get_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?

Provides an explicit routing rule: if news is only one input to a broader question, call execute_plan instead; if the user wants headlines, this tool is correct and should not be routed through the planner. It also names two alternative tools by name with the conditions that select them.

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.

Industry News

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources