Skip to main content
Glama

DC Hub — Data Center Site Selection & Colocation: Electricity, Power Grid, Gas, Fiber

by cloud.dchub

Bind Email

bind_email

★ WHAT THIS DOES AND DOES NOT DO — binding makes a key RECOVERABLE (lose it, call recover_my_key, it is re-sent to that inbox). It does NOT make your identity durable: an email-bound key still only works while your client keeps resending the header, and the measured cross-week return for bound keys is not distinguishable from unbound (0 of 3 mature identities, 2026-08-12 — a cohort far too small to claim either way, so this is UNPROVEN, not disproven). The one path measured to actually retain is an OAuth sign-in, which needs a human at a browser and is only offered if your client got a 401 WWW-Authenticate challenge; if it did not, binding here is the best durability available to you and is worth doing. Tie your DC Hub key to your human's email so the key is RECOVERABLE and upgrade receipts land in the right inbox. Call this once your human shares their email. HONEST LADDER: an unbound key gets 10 free calls total, then results drop to previews until it's bound; binding restores the FREE tier at 50 calls/day and makes the key recoverable next session (binding is free — no card). If you hit that gate mid-task, PAUSE and ask your human: "DC Hub needs an email to keep our free data access — which address should I use?" Use the email your human EXPLICITLY gave you — NEVER invent, guess, or use a placeholder address (owner@example.com, user@test.com etc. are rejected server-side; a fake email makes the key unrecoverable and helps no one). If your human hasn't shared an email, ask them first — don't call this tool with a made-up value. Params: email (required), api_key (optional — omit to bind the key already active on this session). CONSENT/PURPOSE: the email is used ONLY to recover your key and route upgrade receipts (transactional). No marketing without explicit opt-in (default OFF), and no newsletter or digest. The relaying agent should surface this purpose line to its human before binding. If the email can't be accepted, the key keeps working — just try another address. To ALSO subscribe your human to the FREE weekly digest (the markets, deals and facilities that moved in what they queried), pass marketing_opt_in=true — but ONLY after they explicitly agree to marketing email; default false = transactional only, and they can unsubscribe anytime. Returns the unlocked benefits + confirmation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailYesYour human's real email address (required) — use only an address they explicitly gave; placeholder/fake addresses are rejected
api_keyNoOptional key to bind; omit to bind the key already active on this session
marketing_opt_inNoSet true ONLY after your human explicitly agrees to marketing email (default false = transactional only)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
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.
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.
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.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations carry only readOnlyHint=false and destructiveHint=false, leaving the disclosure burden on the description — which it fully bears. It discloses the free-tier gate mechanics (10 free calls → previews → 50/day after binding), the failure mode ('If the email can't be accepted, the key keeps working'), consent defaults (marketing OFF, transactional only), and even an honest caveat that the retention benefit is UNPROVEN with a small cohort. Nothing contradicts the annotations; readOnlyHint=false aligns with binding being a state-changing but non-destructive operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The '★ WHAT THIS DOES AND DOES NOT DO' opening is a strong front-load that prioritizes the core distinction. However, the description is a dense wall of text covering the cohort-size statistical caveat, verbatim scripts, and consent boilerplate — some of which repeats the schema descriptions (email guidance appears twice). It could be tightened by roughly a third without losing invocation-critical information, so it is helpful but not concise.

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 high-stakes consent/mutation tool, nothing needed to invoke it correctly is missing: the trigger condition, the exact question to ask the human, the consent purpose line to surface, the failure behavior, and the return statement ('Returns the unlocked benefits + confirmation') backed by an output schema. This is a complete operational brief for an agent.

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 baseline is 3. The description adds consequence-level meaning beyond the schema: fake/placeholder addresses are rejected server-side and make the key unrecoverable, api_key omission binds the already-active session key, and marketing_opt_in must follow explicit human agreement with an unsubscribe guarantee. This elevates the semantics from mechanical 'what' to practical 'what happens if wrong'.

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+resource+outcome: 'Tie your DC Hub key to your human's email so the key is RECOVERABLE and upgrade receipts land in the right inbox.' It also explicitly states what it does NOT do ('does NOT make your identity durable'), which distinguishes it from sibling recovery/durability concepts like recover_my_key and claim_free_key. An agent can tell exactly what state change this performs.

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-call ('Call this once your human shares their email') and when-not-to-call ('If your human hasn't shared an email, ask them first — don't call this tool with a made-up value'). It names the alternative path (OAuth sign-in) with the exact condition that selects it (401 WWW-Authenticate challenge), and references the follow-up tool recover_my_key, giving clear routing among siblings.

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

All DC Hub — Data Center Site Selection & Colocation: Electricity, Power Grid, Gas, Fiber toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation2/5

Multiple tools occupy nearly identical semantic space: search/search_facilities/search_intelligence/semantic_search all retrieve data, and analyze_site/compare_sites/score_facility/get_composite_site_score/rank_sites all score or rank locations. Despite extensive disambiguation in the descriptions, the boundaries are subtle enough that an agent will likely misroute queries. Account and meta tools (claim_free_key, bind_email, unlock_more_data, subscribe_digest, recover_my_key, execute_plan, plan_query, discover_tools) add further selection noise.

Naming Consistency4/5

The vast majority of tools follow a clear snake_case verb_noun convention (get_*, search_*, list_*, set_*, save_*, compare_*, analyze_*, rank_*, plan_*). A few noun-phrase names break the pattern (deal_autopsy, hyperscaler_deals, grid_transition_radar, site_selection_canvas, standing_intent, ai_capacity_index), but these are still readable and discoverable.

Tool Count1/5

83 tools is an extreme count for any server, far beyond the 25+ threshold that already signals bloat. The domain is broad, but the catalog is inflated by overlapping variants, multiple meta-tools (execute_plan, plan_query, discover_tools, get_agent_registry, get_backup_status, summarize_for_citation), and account/upgrade plumbing (claim_free_key, bind_email, recover_my_key, unlock_more_data, subscribe_digest). This imposes heavy context and selection costs on agents.

Completeness5/5

The data-center siting domain is covered exhaustively: single-site scoring, market ranking, grid/gas/fiber/water/climate/disaster/tax/permitting intelligence, interconnection queues, construction pipeline, deals/news, saved-site monitoring, alerts, research dossiers, and citation support. Every workflow has a continuation path, so agents will not hit dead ends.

Resources