DC Hub — Data Center & Energy Intelligence

Search Intelligence

search_intelligence

Read-onlyIdempotent

Search data-center and energy intelligence by meaning. Retrieve top relevant news, deals, facilities, and market narratives with citable sources from natural-language queries.

Instructions

Semantic (meaning-based) search over DC Hub's live intelligence corpus — industry news, M&A deals, discovered facilities and per-market DCPI analysis narratives — returning the most relevant records with citable source fields. This is the agent-friendly alias over the SAME retrieval layer as semantic_search: same results, different call shape. It takes query plus human-readable corpus names (news | deals | facilities | market_narratives); semantic_search takes q plus the raw table names. Call ONE of them, not both. Params: query (required, natural language); corpus (optional CSV of the four names above, default all); limit (1-15, default 8). BEHAVIOUR: read-only — it writes nothing, and repeat calls with the same arguments return the same records. ACCESS: works with no key, but anonymous results come back as a TRIMMED PREVIEW; the session X-API-Key hydrates full depth per key, and the free tier is capped per day (call claim_free_key once — no email — if you do not hold a key). Do NOT use when you can filter exactly: search_facilities for structured facility filters, get_news for date/keyword news, list_transactions for deal filters — those match fields and return complete sets, where this ranks by meaning and returns a top-N.

Input Schema

TableJSON Schema

Name	Required	Description
`q`	No	Alias for query
`limit`	No	Max results to return, 1-15 (default 8)
`query`	No	Natural-language query (required), e.g. "grids opening up for AI load in the Southeast"
`corpus`	No	Optional corpus to restrict to: news \| deals \| facilities \| market_narratives. CSV of several is allowed; default searches all.

Output Schema

TableJSON Schema

Name	Required	Description
`quota`	No	Caller quota state (remaining calls, tier) when available.
`_entity`	No	Payload class discriminator (e.g. facility\|market\|iso_grid\|queue_results\|deal\|report\|response) — branch on this before parsing the rest.
`citation`	No	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`	No	Collection-level provenance block: {source, method, as_of, verification_counts, cite_url_template, license, cite_as}. Quote the verification level when citing.
`_front_door`	No	In-band front-door hint (first workflow-entry tool of a session): call plan_query(intent) first for the ordered multi-step plan.
`_return_loop`	No	Suggested next-session delta call (get_changes since=24h) so you pull only what changed.
`site_evaluation_handoff`	No	Pre-built follow-up calls (analyze_site / get_water_risk args) when the payload carries coordinates — an array of {tool, parameters, why} entries.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedAug 30, 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 changedv2.3.20Aug 14, 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 changedv2.3.12Jul 28, 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"
+    },
+    "_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": {
+      "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": {
+      "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"
+}

Addedv2.3.7Jul 5, 2026

TDQS

A4.8/5.0

Behavior5/5

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

While annotations already declare readOnlyHint and idempotentHint, the description adds substantive behavioral context: read-only writes nothing, repeat calls return same records, anonymous results are TRIMMED PREVIEW, session X-API-Key hydrates full depth, and free tier is capped per day. It also reveals the key/authentication requirement nuance and points to claim_free_key and unlock_more_data, far exceeding the annotation baseline.

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?

The description is dense but well-organized with labeled sections (Params, BEHAVIOUR, ACCESS, and the exclusion note). Every sentence carries functional weight; however, it is fairly long and partially repeats schema content, so it is not as lean as the highest tier of descriptions.

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?

Given the output schema exists and annotations cover safety/hints, the description supplies all remaining essentials: corpus options, parameter semantics, behavior, access limitations, rate caps, and clear routing to alternatives. An agent has everything needed to decide whether and how to invoke this tool.

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 the schema already documents each parameter. The description adds meaningful usage nuance: query is natural language with a concrete example, corpus can be a CSV of human-readable names, limit is bounded 1-15, and q is explicitly an alias. This reinforces and slightly extends the schema, though much is redundant with it.

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?

The description opens with a specific verb and resource: semantic search over DC Hub's live intelligence corpus, naming the corpora (industry news, M&A deals, discovered facilities, DCPI narratives) and the outcome (most relevant records with citable source fields). It also distinguishes itself from semantic_search by calling out the alias relationship and different parameter shape, so an agent can tell them apart without inspecting schemas.

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?

The description gives explicit when-to-use guidance: 'Do NOT use when you can filter exactly' and names the exact sibling tools (search_facilities, list_transactions, get_news) as alternatives for structured filters. It also warns 'Call ONE of them, not both' regarding semantic_search, leaving no ambiguity about selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server