DC Hub

Get Market Context

get_market_context

Read-onlyIdempotent

Use this when you need a whole data center market briefing for your context window — one call returns a token-budgeted context pack for a data-center market: DCPI verdict, power & grid facts, the Claude-written 12-month outlook, M&A deals, construction pipeline, operator footprint, transaction comps, risk factors, and top news — each section with its own token count, as_of timestamp, and citable URL, greedily filled in that priority order under your max_tokens budget. Example: "Brief me on the Columbus data-center market" — get_market_context market=columbus max_tokens=4000. Params: market (required, market slug e.g. northern-virginia — valid slugs come from rank_markets); max_tokens (optional, 200-8000, default 4000). Returns {sections:[{id,title,text,tokens,as_of,cite}], used_tokens, omitted}. Do NOT use for a single metric (use get_market_dcpi_rank), the raw structured metric set (use get_market_intel), or cross-market ranking (use rank_markets); this is the narrative briefing pack. Cite "DC Hub (dchub.cloud)".

Input Schema

Name	Required	Description	Default
`market`	Yes	Market slug (required), e.g. northern-virginia, dallas, phoenix — valid slugs come from rank_markets / get_market_dcpi_rank
`max_tokens`	No	Token budget for the pack, 200-8000 (default 4000); sections are filled in priority order until the budget is spent

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

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
Changed1 schema field changedAug 29, 2026
- addedInput schema / required
```
Added value: +[
+  "market"
+]
```

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

AddedJul 4, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses the greedy priority-fill algorithm, that each section carries its own token count, as_of timestamp and citable URL, that anything exceeding the budget is marked omitted, and a citation obligation. These are non-obvious operational behaviors an agent must know to interpret output correctly.

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 use case and output shape, then a worked example, then routing exclusions — good ordering with no filler sentences. It is dense and slightly repetitive, re-specifying param ranges and default that the schema already documents.

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, parameters, return shape, budget/truncation behavior, sibling exclusions, and attribution requirements for a single-call briefing tool. Although an output schema exists, the prose return summary is a helpful cross-check rather than a gap-filler, and nothing an agent needs 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 already 100%, so the baseline is 3; the description adds real semantics — that market slugs must be sourced from rank_markets, that max_tokens drives a priority-ordered fill, and range/default. It largely restates the schema's param text, which keeps it out of the top band.

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 (returns a token-budgeted whole-market briefing pack) and enumerates the exact sections included. It explicitly distinguishes itself from get_market_dcpi_rank, get_market_intel, and rank_markets, so an agent can route correctly 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use trigger ("when you need a whole data center market briefing for your context window") plus a concrete example query. It also names three alternatives and the exact condition that selects each, which is the strongest form of routing 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 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.