Skip to main content
Glama
azmartone67

DC Hub — Data Center & Energy Intelligence

Search Facilities

search_facilities
Read-onlyIdempotent

Find data center facilities worldwide by location, power capacity, operator, or fiber connectivity. Filter 17,500+ existing facilities to match your criteria and get key details like MW and status.

Instructions

FRONT DOOR CHECK — if the ask is "find MW in " or otherwise wants power / fiber / water / verdict context ATTACHED to the hits, call execute_plan(intent="<the user's question, unchanged>") instead of hand-chaining this with three more tools. If the ask is a plain inventory lookup — which facilities match these filters — search_facilities IS the right call and costs one round trip; the planner would add steps and latency for nothing. Search 17,500+ global data center facilities across 170+ countries — by location (country/state/market), capacity (MW), operator, fiber connectivity, status (operational/under-construction/planned), or DCPI verdict. Returns name, provider, lat/lon, power_mw, fiber count, market_slug, status. Try: search_facilities country=US state=VA min_capacity_mw=10. Note: status is RETURNED but is not a filter — there is no status or min_mw parameter; to filter by construction stage use get_pipeline. Use this to find EXISTING facilities; do NOT use for the forward-looking construction pipeline (use get_pipeline) or for the full profile of one facility (use get_facility).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNoCity name to filter facilities, e.g. Ashburn, Dallas
tierNoUptime Institute tier filter (1-4)
limitNoMax results to return (1-500; default varies by tool)
queryNoFree-text search over facility name/operator/location (mapped to the backend `q` param), e.g. "hyperscale Ashburn"
stateNoUS state abbreviation or region, e.g. VA, TX
offsetNoPagination offset, 0-based (skip this many results)
countryNoISO 3166-1 alpha-2 country code, e.g. US, GB, SG
operatorNoOperator/provider company name, e.g. Equinix, Digital Realty
max_capacity_mwNoMaximum power capacity filter in megawatts (MW)
min_capacity_mwNoMinimum power capacity filter in megawatts (MW)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNoFacility rows matching the filters
noteNoServing note (e.g. how many rows the full tier returns)
tierNoTier the response was served at
countNoRows returned in THIS response (null on some gated tiers)
quotaNoCaller quota state (remaining calls, tier) when available.
_entityNoPayload class discriminator (e.g. facility|market|iso_grid|queue_results|deal|report|response) — branch on this before parsing the rest.
successNotrue when the search executed
citationNoMachine-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.
provenanceNoCollection-level provenance block: {source, method, as_of, verification_counts, cite_url_template, license, cite_as}. Quote the verification level when citing.
_front_doorNoIn-band front-door hint (first workflow-entry tool of a session): call plan_query(intent) first for the ordered multi-step plan.
_return_loopNoSuggested next-session delta call (get_changes since=24h) so you pull only what changed.
total_matchingNoTotal rows matching the filter across the dataset (null when withheld by tier)
full_results_availableNofalse when the row set was trimmed for your tier
site_evaluation_handoffNoPre-built follow-up calls (analyze_site / get_water_risk args) when the payload carries coordinates — an array of {tool, parameters, why} entries.
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds significant behavioral nuance beyond annotations: it spells out the exact return fields, notes that 'status is RETURNED but is not a filter', clarifies there is no `status` or `min_mw` parameter, and directs construction-stage filtering to get_pipeline. This gives the agent crucial expectations about behavior and limitations without contradicting annotations.

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?

The description is long but every section earns its place: front-door decision rule, tool scope, return fields, example, parameter caveat, and explicit exclusions. It is well-structured with clear markers and front-loads the most critical usage decision. No filler or redundant repetition of the schema.

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 high sibling count and complex decision space, the description is remarkably complete. It addresses when to use vs alternatives, what results look like, and common pitfalls (status filterm min_mw confusion). An output schema exists, so return-value details are covered there; the description adds the strategic context needed for correct tool selection.

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 description coverage is 100%, so baseline is 3. The description adds value by providing a working example (country=US state=VA min_capacity_mw=10) and explicitly clarifying that `status` and `min_mw` are NOT parameters, preventing common misuse. It also mentions capacity filters (MW) in the overview, reinforcing parameter meaning beyond the schema.

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 clearly states the tool's purpose: 'Search 17,500+ global data center facilities' with specific filter dimensions (location, capacity, operator, fiber, status, DCPI verdict). It distinguishes itself from siblings by explicitly naming alternatives: 'use get_pipeline' for construction pipeline, 'use get_facility' for full profile, and 'call execute_plan' when context is needed. This is a specific verb+resource with scope and differentiation.

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 explicit when-to-use vs alternatives: 'If the ask is a plain inventory lookup... search_facilities IS the right call' versus 'call execute_plan... instead' for context-attached asks. Also gives exclusions: 'do NOT use for the forward-looking construction pipeline (use get_pipeline) or for the full profile (use get_facility).' Includes a concrete example query to illustrate proper usage.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/azmartone67/dchub-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server