DC Hub

Market Intelligence Index

get_intelligence_index

Read-onlyIdempotent

Real-time composite market health score (0-100) aggregating supply/demand balance, vacancy, absorption velocity, fiber depth, power availability, and pricing trend. Returns the index value, percentile rank across the 300+ market set, 7d/30d trend direction, and underlying component scores. Answers "is this market healthy", "how does Northern Virginia look overall right now". Try: get_intelligence_index market=northern-virginia. Returns ONE composite health number for a market; do NOT use for the full market metric set (use get_market_intel) or to rank multiple markets (use rank_markets).

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`quota`	No	Caller quota state (remaining calls, tier).
`_entity`	No	Payload class (facility\|market\|iso_grid\|queue_results\|deal\|report\|response); branch on it.
`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"
+}

Changed3 schema fields changedApr 29, 2026

addedInput schema / $schema

Added value: +"http://json-schema.org/draft-07/schema#"

removedInput schema / title

Removed value: -"get_intelligence_indexArguments"

changedOutput schema / (root)

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

Changed1 schema field changedApr 11, 2026

changedOutput schema / (root)

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

Changed1 schema field changedMar 26, 2026

changedOutput schema / (root)

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

First observedMar 6, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: what the composite aggregates and what comes back (index value, percentile rank across the 300+ market set, 7d/30d trend, component scores). It stops short of discussing data freshness, staleness windows, or coverage limits, so 4 rather than 5.

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-loads the definition, then outputs, then natural-language triggers, then the sibling routing, then an example. Dense but every sentence carries distinct information and none restates the name or title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so the description is not obligated to detail return values (though it helpfully does). The real completeness gap is the phantom `market` parameter: with no scoping parameter in the schema, it is unclear how the single composite score is selected, and the example reinforces a call signature that cannot work. Everything else an agent needs is present.

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?

The schema declares zero properties, which would normally be a baseline 4, but the description supplies an example invocation with a `market` argument ("get_intelligence_index market=northern-virginia") that the empty input schema cannot accept. Rather than clarifying parameters, this invents one and would lead an agent to a validation error, so it sits below the zero-param baseline.

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 (composite market health score), defines the 0-100 range, enumerates the aggregated inputs (supply/demand balance, vacancy, absorption velocity, fiber depth, power availability, pricing trend), and explicitly contrasts itself with get_market_intel and rank_markets. An agent can select it 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?

Gives both a positive trigger ("is this market healthy", "how does Northern Virginia look overall right now") and explicit exclusions naming the correct siblings: get_market_intel for the full metric set and rank_markets for ranking. This is textbook when/when-not/alternative 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.

Market Intelligence Index

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources