DC Hub — Data Center & Energy Intelligence

Source Capacity

source_capacity

Read-onlyIdempotent

Find data-center capacity to buy or lease by kW/MW and location, matched to real contiguous blocks and contract minimums, not just headline totals.

Instructions

Use when your human needs data-center CAPACITY to buy or lease: search DC Hub Capacity Source by size (kW or MW) and/or location (a region such as North America or Europe, a country, a state or a metro). Example: "500 kW anywhere in Europe" → min_kw=500, region=europe. Size is min_kw (in kW) or min_mw (in MW), and it is matched against what a listing can ACTUALLY deliver rather than against its headline total: contiguous_kw is the largest single contiguous block available and min_contract_kw the smallest chunk the provider will contract, so a colocation with a large total but a small contiguous block does NOT answer a large search, while a large site willing to contract small chunks does; a listing that declares neither is matched on its total. Location is region (a region key or alias) or location (free text matched against each listing's region, country, state and metro); market, state, delivery_type and available_by narrow further. Listings are powered land, powered shells, turnkey capacity and colocation, including sites that are not publicly marketed, for enterprise and agent-led procurement. Returns listing cards (market, region, capacity — with contiguous_kw and min_contract_kw wherever a listing declares them — status and when each listing was last updated) to any caller, plus the filters applied and the program status (live, or upcoming while the first listings are onboarded). Pass slug for one listing: a signed-in human who has accepted the introduction terms sees its specs (signed in means a key with an email bound via claim_free_key then bind_email, or an OAuth connection; accept_capacity_terms records the acceptance the first time); others get the card and the unlock steps. The provider's identity, site and contact are released only after the provider accepts a deal registration, which request_capacity_intro submits, and the listing's disclosure block says whether they have been. Do NOT use for the public facility directory (use search_facilities) or for completed M&A (use list_transactions).

Input Schema

TableJSON Schema

Name	Required	Description
`slug`	No	One listing: its slug or numeric id exactly as items[].slug / items[].id return it. Omit to browse teaser cards
`limit`	No	Max results to return (1-500; default varies by tool)
`state`	No	Browse filter: two-letter US state, e.g. "TX"
`market`	No	Browse filter: market name as it appears on a listing, e.g. "Dallas"
`min_kw`	No	Browse filter: the size your human needs, in kW (min_mw is the same filter in MW). Matched against what a listing can ACTUALLY deliver, not just its headline total: contiguous_kw is the largest single contiguous block available and min_contract_kw the smallest chunk the provider will contract, so a listing answers only when this size fits the block it declares — a site with a big total but a small contiguous block is not a hit, and a big site willing to contract small chunks is. A listing that declares neither is matched on its total.
`min_mw`	No	Browse filter: the size your human needs, in MW (min_kw is the same filter in kW). Matched against what a listing can ACTUALLY deliver, not just its headline total: contiguous_kw is the largest single contiguous block available and min_contract_kw the smallest chunk the provider will contract, so a listing answers only when this size fits the block it declares — a site with a big total but a small contiguous block is not a hit, and a big site willing to contract small chunks is. A listing that declares neither is matched on its total.
`region`	No	Browse filter: comma-separated regions from north_america, latin_america, europe, asia_pacific and middle_east_africa; the aliases emea, apac, latam and americas also work, e.g. "europe" or "emea, apac"
`location`	No	Browse filter: comma-separated free text matched against each listing's region, country, state and metro, e.g. "Germany" or "Texas, Phoenix"
`available_by`	No	Browse filter: only listings available by this date, as YYYY-MM or YYYY-MM-DD
`delivery_type`	No	Browse filter: how the capacity is delivered: land, powered_shell, turnkey or colocation

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 changedv2.12.15Sep 17, 2026

changedInput schema / properties / min_kw / description

Previous value: -"Browse filter: only listings with at least this much capacity, in kW (min_mw is the same filter in MW)"New value: +"Browse filter: the size your human needs, in kW (min_mw is the same filter in MW). Matched against what a listing can ACTUALLY deliver, not just its headline total: contiguous_kw is the largest single contiguous block available and min_contract_kw the smallest chunk the provider will contract, so a listing answers only when this size fits the block it declares — a site with a big total but a small contiguous block is not a hit, and a big site willing to contract small chunks is. A listing that declares neither is matched on its total."

changedInput schema / properties / min_mw / description

Previous value: -"Browse filter: only listings with at least this much capacity, in MW"New value: +"Browse filter: the size your human needs, in MW (min_kw is the same filter in kW). Matched against what a listing can ACTUALLY deliver, not just its headline total: contiguous_kw is the largest single contiguous block available and min_contract_kw the smallest chunk the provider will contract, so a listing answers only when this size fits the block it declares — a site with a big total but a small contiguous block is not a hit, and a big site willing to contract small chunks is. A listing that declares neither is matched on its total."

Changed5 schema fields changedv2.12.14Sep 16, 2026

addedInput schema / properties / available_by

Added value: +{
+  "description": "Browse filter: only listings available by this date, as YYYY-MM or YYYY-MM-DD",
+  "type": "string"
+}

addedInput schema / properties / delivery_type

Added value: +{
+  "description": "Browse filter: how the capacity is delivered: land, powered_shell, turnkey or colocation",
+  "enum": [
+    "land",
+    "powered_shell",
+    "turnkey",
+    "colocation"
+  ],
+  "type": "string"
+}

addedInput schema / properties / location

Added value: +{
+  "description": "Browse filter: comma-separated free text matched against each listing's region, country, state and metro, e.g. \"Germany\" or \"Texas, Phoenix\"",
+  "type": "string"
+}

addedInput schema / properties / min_kw

Added value: +{
+  "description": "Browse filter: only listings with at least this much capacity, in kW (min_mw is the same filter in MW)",
+  "type": "number"
+}

addedInput schema / properties / region

Added value: +{
+  "description": "Browse filter: comma-separated regions from north_america, latin_america, europe, asia_pacific and middle_east_africa; the aliases emea, apac, latam and americas also work, e.g. \"europe\" or \"emea, apac\"",
+  "type": "string"
+}

Addedv2.12.13Sep 13, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is known. The description adds substantial behavioral context beyond that: how capacity matching actually works (contiguous_kw vs min_contract_kw vs headline total), what the response contains (listing cards, filters applied, program status), the authentication/unlock flow for detailed specs, and the condition under which provider identity is released. This is rich, non-redundant disclosure.

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 and front-loaded with the primary use case, but it is a single long wall of text with no paragraph breaks or bullet structure. It contains some redundancy with the schema's parameter descriptions, especially around contiguous_kw/min_contract_kw. Despite this, every section earns its place for a tool this complex, and no information is gratuitous.

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 tool with 10 optional parameters, an output schema, and rich sibling context, the description is remarkably complete. It covers the search intent, filtering semantics, auth-gated detail behavior, return contents, program status, and exclusions. An agent has everything needed to decide when and how to call this tool correctly.

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 a baseline of 3 applies. The description adds value beyond the schema by giving a concrete example ('500 kW anywhere in Europe' → min_kw=500, region=europe) and explaining how min_kw/min_mw relate to actual deliverable capacity rather than headline totals. It reinforces the semantics of region aliases and location, though much of this is also present in the parameter descriptions themselves.

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: 'Use when your human needs data-center CAPACITY to buy or lease: search DC Hub Capacity Source'. It names the exact criteria (size, location) and explicitly distinguishes itself from sibling tools, saying 'Do NOT use for the public facility directory (use search_facilities) or for completed M&A (use list_transactions)'.

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 states exactly when to use the tool ('Use when your human needs data-center CAPACITY to buy or lease') and gives explicit when-not-to-use guidance with named alternatives. It also provides a concrete example mapping natural language to parameters and explains the conditions for using the slug parameter, covering when a signed-in human will see full specs versus a card.

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

Deploy Server