Dchub

Dchub Search Facilities

dchub_search_facilities

Read-onlyIdempotent

Find data centers and who operates them (DC Hub facility registry), filtered by city, state, country, operator or MW range. Returns name, operator, location and verification flag; MW detail needs a DC Hub key. Keyless calls return a preview.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "city": "Ashburn",
      "limit": 3
    },
    "name": "dchub_search_facilities"
  }
}

Input Schema

Name	Required	Description
`city`	No	City, e.g. Ashburn
`limit`	No	Rows to return (default 10)
`query`	No	Free-text search
`state`	No	State code, e.g. VA
`offset`	No	Paging offset
`country`	No	Country code, e.g. US
`operator`	No	Operator, e.g. Equinix
`max_capacity_mw`	No	Maximum MW
`min_capacity_mw`	No	Minimum MW

Output Schema

Name	Required	Description	Default
`result`	No
`source`	No
`preview`	No
`preview_notice`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 28, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds the genuinely useful auth/degradation detail — keyless calls return a preview and MW detail requires a key — but says nothing about result volume or paging behavior beyond that.

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?

Two compact sentences, front-loaded with the purpose and filters, followed immediately by the return/auth caveat. No filler or restatement.

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

Completeness4/5

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

An output schema exists, so return values need not be enumerated, and the description still names the key fields and the keyless-preview behavior. Adequate for a nine-parameter search; only paging and default-limit expectations are left entirely to the schema.

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?

Schema coverage is 100% with nine documented properties, so the schema carries the parameter semantics. The description only enumerates a subset of filters (city, state, country, operator, MW range) and omits query, limit and offset, adding no syntax or format detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — 'Find data centers and who operates them' — and names the registry it searches, plus the filter dimensions. It stops short of naming a sibling such as dchub_source_capacity or dchub_get_grid_data to disambiguate which DC Hub tool to pick.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is implied (search the facility registry) rather than stated as when-to-use/when-not. The one real routing signal is the licensing note that 'MW detail needs a DC Hub key' and keyless calls return a preview, which helps an agent set expectations but doesn't point to an alternative tool.

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

All Dchub 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.