DC Hub — Data Center & Energy Intelligence

Register Standing Intent (webhook push)

register_standing_intent

Set up a webhook watch for new deals, news keywords, or permitting changes. Receive HMAC-signed push alerts to your HTTPS endpoint when new matches appear, without polling.

Instructions

Register a STANDING QUERY with webhook push — DC Hub POSTs an HMAC-signed webhook to YOUR https URL whenever matches grow (push, not poll: "notify my orchestrator on any new deal in Columbus"). Requires a key. Params: kind ("new_deal_in_market" watches deals in the market param · "news_keyword" watches news matching q · "permitting_change" watches published permitting intel, optionally per state), market / q / state (the watch parameter for the chosen kind), webhook_url (your public HTTPS endpoint — private/internal hosts are rejected). Returns {intent_id, secret} — SAVE the secret: every delivery carries X-DCHub-Signature: sha256=HMAC(secret, body). First evaluation initializes the watermark silently; growth fires the webhook; 5 straight delivery failures auto-disable the intent. Evaluated every ~2h. Answers "notify my system whenever a new moratorium appears", "push me new matches instead of making me poll", "tell my orchestrator when a deal lands in Columbus". Try: register_standing_intent kind=news_keyword q=moratorium webhook_url=https://hooks.example.com/dchub. Do NOT use for one-shot reads (get_news / list_transactions) or email alerts (set_market_alert); this is machine-to-machine push.

Input Schema

TableJSON Schema

Name	Required	Description
`q`	No	For news_keyword: the keyword/phrase to watch in title+summary, e.g. moratorium
`kind`	Yes	Watch kind: "new_deal_in_market" \| "news_keyword" \| "permitting_change"
`state`	No	For permitting_change: optional US state filter, e.g. MN
`market`	No	For new_deal_in_market: the market/region substring to watch, e.g. columbus
`webhook_url`	Yes	Your public HTTPS webhook endpoint (required)

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.

Addedv2.12.10Sep 9, 2026

TDQS

A5/5.0

Behavior5/5

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

The description goes far beyond the annotations by revealing authentication requirements ('Requires a key'), delivery details (HMAC-signed webhook, X-DCHub-Signature), lifecycle behavior (watermark initialization, 5-failure auto-disable, ~2h evaluation), and constraints (public HTTPS only). This richly supplements the basic annotation hints.

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 dense but every sentence earns its place: definition, mechanism, examples, parameter semantics, secret handling, failure behavior, evaluation cadence, and alternatives. The structure moves logically from what it is to how to use it to what happens after registration.

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 mutation-like registration tool, the description covers prerequisites, parameter selection, return values, delivery signature, failure semantics, and operational cadence. With output schema indicated and return values named, nothing essential is missing for an agent to select and invoke this tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema coverage is 100%, the description adds significant semantic value by explaining how each kind maps to its watch parameter, giving examples like 'new_deal_in_market' watching deals, and calling out that private/internal hosts are rejected. It also explains the returned {intent_id, secret} and its security importance.

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 states a specific verb and resource ('Register a STANDING QUERY with webhook push') and distinguishes the mechanism from polling ('push, not poll'). It explicitly contrasts with one-shot reads and email alerts, making sibling differentiation immediate.

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?

It gives concrete use cases ('notify my orchestrator on any new deal in Columbus') and explicitly says when NOT to use it: 'Do NOT use for one-shot reads (get_news / list_transactions) or email alerts (set_market_alert)'. It also names delete_standing_intent as the removal counterpart.

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

Deploy Server