DC Hub

Set Site Alert

set_site_alert

Use this when the user wants an email watch on a saved data center site (free with a key) — DC Hub emails you when that site’s DCPI score, grid capacity, or nearby facilities move, so you don’t have to keep re-checking. On the free tier the alert is delivered to your human’s bound email (call bind_email first; notify_email is forced to that address). A paid DC Hub plan can send to any address. The "monitor my shortlist for me" loop: call save_site first (it returns a saved_site_id), then set_site_alert on that id. Params: saved_site_id (required integer, from save_site or list_saved_sites), trigger_type ("dcpi_change" | "capacity_change" | "new_facility_nearby", default "dcpi_change"), threshold (number — the points/MW move that fires it, default 5), notify_email (required — the address the alert is sent to). Answers "let me know if anything changes at the site I saved". Try: set_site_alert saved_site_id=12 trigger_type=dcpi_change threshold=5 notify_email=you@firm.com. Returns {ok, alert_id, message}. Do NOT use to watch a whole MARKET (use set_market_alert) or to save a new site (use save_site); this arms a monitor on ONE already-saved site.

Input Schema

Name	Required	Description
`threshold`	No	The points/MW move that fires the alert (default 5)
`notify_email`	Yes	Email address the alert is sent to (required); on free tier forced to your human's bound email
`trigger_type`	No	What movement fires the alert: "dcpi_change" (default), "capacity_change", or "new_facility_nearby"
`saved_site_id`	Yes	The saved_site_id returned by save_site or list_saved_sites (required)

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedOct 19, 2026
- removedOutput schema / properties / _entity
```
Removed value: -{
-  "type": "string"
-}
```
- removedOutput schema / properties / _front_door
```
Removed value: -{
-  "type": "object"
-}
```
- removedOutput schema / properties / _return_loop
```
Removed value: -{
-  "type": "object"
-}
```
- removedOutput schema / properties / citation
```
Removed value: -{}
```
- removedOutput schema / properties / provenance
```
Removed value: -{
-  "type": "object"
-}
```
- removedOutput schema / properties / quota
```
Removed value: -{
-  "type": "object"
-}
```
- removedOutput schema / properties / site_evaluation_handoff
```
Removed value: -{}
```

Changed19 schema fields changedOct 18, 2026

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 / description

Removed value: -"Payload class (facility|market|iso_grid|queue_results|deal|report|response); branch on it."

removedOutput schema / properties / _front_door / additionalProperties
```
Removed value: -{}
```

removedOutput schema / properties / _front_door / description

Removed value: -"First-tool hint: plan_query(intent) returns the ordered plan."

removedOutput schema / properties / _front_door / properties
```
Removed value: -{}
```
removedOutput schema / properties / _return_loop / additionalProperties
```
Removed value: -{}
```
removedOutput schema / properties / _return_loop / description
```
Removed value: -"Next-session delta call (get_changes)."
```
removedOutput schema / properties / _return_loop / properties
```
Removed value: -{}
```

removedOutput schema / properties / citation / anyOf

Removed value: -[
-  {
-    "additionalProperties": {},
-    "properties": {},
-    "type": "object"
-  },
-  {
-    "type": "string"
-  }
-]

removedOutput schema / properties / citation / description

Removed value: -"How to attribute DC Hub: {source, url, license, cite_as, retrieved_at}, or the attribution line as a string."

removedOutput schema / properties / provenance / additionalProperties
```
Removed value: -{}
```

removedOutput schema / properties / provenance / description

Removed value: -"Source, method, as_of, verification_counts, license, cite_as; quote it when citing."

removedOutput schema / properties / provenance / properties
```
Removed value: -{}
```
removedOutput schema / properties / quota / additionalProperties
```
Removed value: -{}
```

removedOutput schema / properties / quota / description

Removed value: -"Caller quota state (remaining calls, tier)."

removedOutput schema / properties / quota / properties
```
Removed value: -{}
```

removedOutput schema / properties / site_evaluation_handoff / anyOf

Removed value: -[
-  {
-    "items": {
-      "additionalProperties": {},
-      "properties": {},
-      "type": "object"
-    },
-    "type": "array"
-  },
-  {
-    "additionalProperties": {},
-    "properties": {},
-    "type": "object"
-  }
-]

removedOutput schema / properties / site_evaluation_handoff / description

Removed value: -"Follow-up calls [{tool, parameters, why}] when the payload carries coordinates."

AddedOct 9, 2026
RemovedSep 29, 2026
Changed1 schema field changedAug 29, 2026
- addedInput schema / required
```
Added value: +[
+  "saved_site_id",
+  "notify_email"
+]
```

Changed2 schema fields changedAug 21, 2026

removedInput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

removedOutput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

Changed5 schema fields changedAug 11, 2026

removedOutput schema / properties / citation / additionalProperties
```
Removed value: -{}
```

addedOutput schema / properties / citation / anyOf

Added value: +[
+  {
+    "additionalProperties": {},
+    "properties": {},
+    "type": "object"
+  },
+  {
+    "type": "string"
+  }
+]

changedOutput schema / properties / citation / description

Previous value: -"Machine-readable citation: how to attribute DC Hub (dchub.cloud) for this payload."New 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."

removedOutput schema / properties / citation / properties
```
Removed value: -{}
```
removedOutput schema / properties / citation / type
```
Removed value: -"object"
```

Changed1 schema field changedJul 21, 2026

addedOutput schema / properties / _front_door

Added value: +{
+  "additionalProperties": {},
+  "description": "In-band front-door hint (first workflow-entry tool of a session): call plan_query(intent) first for the ordered multi-step plan.",
+  "properties": {},
+  "type": "object"
+}

Changed5 schema fields changedJul 18, 2026

removedOutput schema / properties / site_evaluation_handoff / additionalProperties
```
Removed value: -{}
```

addedOutput schema / properties / site_evaluation_handoff / anyOf

Added value: +[
+  {
+    "items": {
+      "additionalProperties": {},
+      "properties": {},
+      "type": "object"
+    },
+    "type": "array"
+  },
+  {
+    "additionalProperties": {},
+    "properties": {},
+    "type": "object"
+  }
+]

changedOutput schema / properties / site_evaluation_handoff / description

Previous value: -"Pre-built follow-up call (analyze_site / get_water_risk args) when the payload carries coordinates."New value: +"Pre-built follow-up calls (analyze_site / get_water_risk args) when the payload carries coordinates — an array of {tool, parameters, why} entries."

removedOutput schema / properties / site_evaluation_handoff / properties
```
Removed value: -{}
```
removedOutput schema / properties / site_evaluation_handoff / type
```
Removed value: -"object"
```

Changed1 schema field changedJul 17, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "description": "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.",
+  "properties": {
+    "_entity": {
+      "description": "Payload class discriminator (e.g. facility|market|iso_grid|queue_results|deal|report|response) — branch on this before parsing the rest.",
+      "type": "string"
+    },
+    "_return_loop": {
+      "additionalProperties": {},
+      "description": "Suggested next-session delta call (get_changes since=24h) so you pull only what changed.",
+      "properties": {},
+      "type": "object"
+    },
+    "citation": {
+      "additionalProperties": {},
+      "description": "Machine-readable citation: how to attribute DC Hub (dchub.cloud) for this payload.",
+      "properties": {},
+      "type": "object"
+    },
+    "provenance": {
+      "additionalProperties": {},
+      "description": "Collection-level provenance block: {source, method, as_of, verification_counts, cite_url_template, license, cite_as}. Quote the verification level when citing.",
+      "properties": {},
+      "type": "object"
+    },
+    "quota": {
+      "additionalProperties": {},
+      "description": "Caller quota state (remaining calls, tier) when available.",
+      "properties": {},
+      "type": "object"
+    },
+    "site_evaluation_handoff": {
+      "additionalProperties": {},
+      "description": "Pre-built follow-up call (analyze_site / get_water_risk args) when the payload carries coordinates.",
+      "properties": {},
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

Changed4 schema fields changedJul 2, 2026

addedInput schema / properties / notify_email / description

Added value: +"Email address the alert is sent to (required); on free tier forced to your human's bound email"

addedInput schema / properties / saved_site_id / description

Added value: +"The saved_site_id returned by save_site or list_saved_sites (required)"

addedInput schema / properties / threshold / description

Added value: +"The points/MW move that fires the alert (default 5)"

addedInput schema / properties / trigger_type / description

Added value: +"What movement fires the alert: \"dcpi_change\" (default), \"capacity_change\", or \"new_facility_nearby\""

AddedJun 19, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare this is a non-readonly, non-destructive, non-idempotent mutation. The description adds real context beyond that: free-tier delivery is forced to the bound email, bind_email is a hard precondition, and it returns {ok, alert_id, message}. It does not spell out tier/permission failure behavior, but the added value over annotations is substantial.

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?

Dense but front-loaded with the core purpose, then preconditions, then the workflow, then params, example, return shape, and exclusions. Several clauses are mildly redundant but almost every sentence carries operative content; a small trim would help.

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 stateful mutation with preconditions, the description covers the prerequisite chain, tier constraints, parameter meanings, an invocation example, and the return shape. An agent has everything needed to call it correctly on the first attempt.

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 baseline is 3, but the description adds meaning the schema does not: which is required, that saved_site_id comes from save_site/list_saved_sites, the trigger_type semantics, threshold units, and the free-tier override that forces notify_email to the bound address.

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 (arm an email watch on a saved site) and names exactly what it distinguishes from siblings: set_market_alert for whole markets and save_site for creating a site. An agent can route between all three alert tools 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?

Gives explicit when-to-use ('let me know if anything changes at the site I saved'), prerequisites (bind_email first on free tier, save_site first in the loop), and explicit exclusions with named alternatives. 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.

All DC Hub 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.