Skip to main content
Glama
azmartone67

DC Hub: Data Center, Power Grid & Energy Intelligence

Request Capacity Intro

request_capacity_intro

Request a data center capacity introduction for a specific listing or upcoming capacity requirement; registers the deal and shares only your company name and requirement until provider accepts.

Instructions

Use this when the user wants data center capacity behind a Capacity Source listing (pass slug), or wants first access to capacity matching a requirement as listings are onboarded (omit slug; pass capacity_mw or capacity_kw, markets, states, regions or countries, and timeline). This registers a deal: DC Hub records the request in its lead register and sends the provider ONLY your human's company name and the requirement. The provider accepts or declines. Only if the provider accepts does DC Hub share the provider's identity, site details and contact with your human, and your human's name, role and email with the provider; on a decline nothing is shared. Requires an identified caller (claim_free_key, then bind_email with your human's address) and accept_terms=true only after your human has read and agreed to the introduction terms at https://dchub.cloud/listings#terms. Returns lead_id, status and the next step. For a listing, source_capacity with its slug then shows the deal status in the disclosure block and, once the provider accepts, the provider's identity, site and contact. Do NOT use to save or monitor a site (use save_site / set_site_alert).

Input Schema

NameRequiredDescriptionDefault
nameNoYour human's full name. Nothing is sent without it; use only what they gave you, never invent it
roleNoYour human's role or title
slugNoThe listing to register a deal for: its slug or id from source_capacity. Omit to register a standing requirement for upcoming listings instead
notesNoAnything else the provider should know about the requirement. It travels with the requirement, so leave out anything that identifies your human
statesNoComma-separated US states of interest, e.g. "TX, AZ"
companyNoYour human's company. Nothing is sent without it
marketsNoComma-separated markets of interest, e.g. "Dallas, Phoenix"
messageNoA short note from your human for the provider. The deal registration itself carries only the company name and the requirement
regionsNoComma-separated regions of interest from north_america, latin_america, europe, asia_pacific and middle_east_africa (aliases emea, apac, latam, americas), e.g. "europe, apac"
timelineNoWhen the capacity is needed, e.g. a quarter and year
use_caseNoWhat the capacity is for, e.g. "AI inference"
countriesNoComma-separated countries of interest, e.g. "Germany, Netherlands"
capacity_kwNoCapacity needed, in kW (capacity_mw is the same requirement in MW)
capacity_mwNoCapacity needed, in MW
accept_termsNoSet true ONLY after your human has read and agreed to the introduction terms at https://dchub.cloud/listings#terms. Unless it is exactly true, nothing is sent
terms_versionNoThe terms version your human agreed to, e.g. program.terms.version from source_capacity. Omit to send the version currently published

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv2.12.45
    • changedOutput schema / additionalProperties
      Previous value: -{}New value: +true
    • removedOutput schema / description
      Removed value: -"DC Hub envelope: tool data fields ride at the top level beside these keys."
    • removedOutput schema / properties / _entity
      Removed value: -{
      -  "description": "Payload class (facility|market|iso_grid|queue_results|deal|report|response); branch on it.",
      -  "type": "string"
      -}
    • removedOutput schema / properties / _front_door
      Removed value: -{
      -  "additionalProperties": {},
      -  "description": "First-tool hint: plan_query(intent) returns the ordered plan.",
      -  "properties": {},
      -  "type": "object"
      -}
    • removedOutput schema / properties / _return_loop
      Removed value: -{
      -  "additionalProperties": {},
      -  "description": "Next-session delta call (get_changes).",
      -  "properties": {},
      -  "type": "object"
      -}
    • removedOutput schema / properties / citation
      Removed value: -{
      -  "anyOf": [
      -    {
      -      "additionalProperties": {},
      -      "properties": {},
      -      "type": "object"
      -    },
      -    {
      -      "type": "string"
      -    }
      -  ],
      -  "description": "How to attribute DC Hub: {source, url, license, cite_as, retrieved_at}, or the attribution line as a string."
      -}
    • removedOutput schema / properties / provenance
      Removed value: -{
      -  "additionalProperties": {},
      -  "description": "Source, method, as_of, verification_counts, license, cite_as; quote it when citing.",
      -  "properties": {},
      -  "type": "object"
      -}
    • removedOutput schema / properties / quota
      Removed value: -{
      -  "additionalProperties": {},
      -  "description": "Caller quota state (remaining calls, tier).",
      -  "properties": {},
      -  "type": "object"
      -}
    • removedOutput schema / properties / site_evaluation_handoff
      Removed value: -{
      -  "anyOf": [
      -    {
      -      "items": {
      -        "additionalProperties": {},
      -        "properties": {},
      -        "type": "object"
      -      },
      -      "type": "array"
      -    },
      -    {
      -      "additionalProperties": {},
      -      "properties": {},
      -      "type": "object"
      -    }
      -  ],
      -  "description": "Follow-up calls [{tool, parameters, why}] when the payload carries coordinates."
      -}
  2. Changed8 schema fields changedv2.12.43
    • changedOutput schema / description
      Previous value: -"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."New value: +"DC Hub envelope: tool data fields ride at the top level beside these keys."
    • changedOutput schema / properties / _entity / description
      Previous value: -"Payload class discriminator (e.g. facility|market|iso_grid|queue_results|deal|report|response) — branch on this before parsing the rest."New value: +"Payload class (facility|market|iso_grid|queue_results|deal|report|response); branch on it."
    • changedOutput schema / properties / _front_door / description
      Previous value: -"In-band front-door hint (first workflow-entry tool of a session): call plan_query(intent) first for the ordered multi-step plan."New value: +"First-tool hint: plan_query(intent) returns the ordered plan."
    • changedOutput schema / properties / _return_loop / description
      Previous value: -"Suggested next-session delta call (get_changes since=24h) so you pull only what changed."New value: +"Next-session delta call (get_changes)."
    • changedOutput schema / properties / citation / description
      Previous 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."New value: +"How to attribute DC Hub: {source, url, license, cite_as, retrieved_at}, or the attribution line as a string."
    • changedOutput schema / properties / provenance / description
      Previous value: -"Collection-level provenance block: {source, method, as_of, verification_counts, cite_url_template, license, cite_as}. Quote the verification level when citing."New value: +"Source, method, as_of, verification_counts, license, cite_as; quote it when citing."
    • changedOutput schema / properties / quota / description
      Previous value: -"Caller quota state (remaining calls, tier) when available."New value: +"Caller quota state (remaining calls, tier)."
    • changedOutput schema / properties / site_evaluation_handoff / description
      Previous value: -"Pre-built follow-up calls (analyze_site / get_water_risk args) when the payload carries coordinates — an array of {tool, parameters, why} entries."New value: +"Follow-up calls [{tool, parameters, why}] when the payload carries coordinates."
  3. Changed6 schema fields changedv2.12.14
    • addedInput schema / properties / capacity_kw
      Added value: +{
      +  "description": "Capacity needed, in kW (capacity_mw is the same requirement in MW)",
      +  "type": "number"
      +}
    • addedInput schema / properties / countries
      Added value: +{
      +  "description": "Comma-separated countries of interest, e.g. \"Germany, Netherlands\"",
      +  "type": "string"
      +}
    • changedInput schema / properties / message / description
      Previous value: -"A short note from your human to the operator"New value: +"A short note from your human for the provider. The deal registration itself carries only the company name and the requirement"
    • changedInput schema / properties / notes / description
      Previous value: -"Anything else the operator should know about the requirement"New value: +"Anything else the provider should know about the requirement. It travels with the requirement, so leave out anything that identifies your human"
    • addedInput schema / properties / regions
      Added value: +{
      +  "description": "Comma-separated regions of interest from north_america, latin_america, europe, asia_pacific and middle_east_africa (aliases emea, apac, latam, americas), e.g. \"europe, apac\"",
      +  "type": "string"
      +}
    • changedInput schema / properties / slug / description
      Previous value: -"The listing to request an introduction for: its slug or id from source_capacity. Omit to register a standing requirement for upcoming listings instead"New value: +"The listing to register a deal for: its slug or id from source_capacity. Omit to register a standing requirement for upcoming listings instead"
  4. Addedv2.12.13

TDQS

A4.6/5.0
Behavior4/5

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

Annotations only tell the agent it is a non-readonly, non-destructive mutation; the description adds substantial context beyond that: it registers a lead, sends the provider ONLY the company name and requirement, shares identity/site/contact only on acceptance and nothing on decline, and requires an identified caller (claim_free_key then bind_email) plus accept_terms=true. This is exactly the kind of disclosure annotations cannot carry. It stops short of the very top only because idempotency/retry behavior on a duplicate request is unaddressed.

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?

Front-loaded with the triggering condition ("Use this when...") and every sentence carries operational weight (modes, privacy behavior, prerequisites, follow-up). It is dense and long, but not padded or repetitive.

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 16-parameter, privacy-sensitive deal-registration tool with no output schema details needed from the description, it covers prerequisites, consent gating, disclosure semantics, mode selection, follow-up and exclusions. An agent has everything required to invoke it correctly and safely.

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 goes further by clustering parameters into the two operating modes (slug vs capacity_mw/capacity_kw, markets, states, regions, countries, timeline), which tells the agent which fields matter in which flow. It does not add syntax beyond that, so it earns a 4 rather than 5.

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?

Specific verb+resource (register a deal / request a capacity introduction) with the two distinct modes (slug vs standing requirement) spelled out, and it explicitly names the siblings it is not (save_site / set_site_alert). An agent can distinguish it from source_capacity, register_standing_intent and save_site without opening a schema.

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?

States exactly when to use each mode (pass slug for a listing, omit slug plus capacity/markets/timeline for first access to upcoming listings), names the follow-up path (source_capacity shows status once registered), and gives an explicit exclusion with alternatives (do NOT use to save or monitor a site). Nothing is left to inference.

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

Deploy Server

Other Tools