Skip to main content
Glama

set_site_alert

Arm an email alert on a saved site to monitor DCPI, capacity, or nearby facility changes, so you get notified instead of manually re-checking.

Instructions

Arm an email watch on a site you already saved (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). Pro 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). 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

TableJSON Schema
NameRequiredDescriptionDefault
thresholdNoThe points/MW move that fires the alert (default 5)
notify_emailNoEmail address the alert is sent to (required); on free tier forced to your human's bound email
trigger_typeNoWhat movement fires the alert: "dcpi_change" (default), "capacity_change", or "new_facility_nearby"
saved_site_idNoThe saved_site_id returned by save_site or list_saved_sites (required)
Behavior4/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, so the description adds value by explaining the alert delivery mechanism (email), the free tier constraint (forced to bound email), and the return format ({ok, alert_id, message}). This provides useful context beyond the annotations.

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?

The description is well-structured, starting with the core purpose, then detailing parameters, usage notes, and exclusions. It is slightly verbose but every sentence adds value. The front-loading of the main action and example makes it easy to parse.

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?

Given no output schema, the description covers the return format. All four parameters are fully explained with types, defaults, and dependencies. The workflow prerequisites and free-tier constraints are documented. For a mutation tool with multiple dependencies, the description is complete.

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. The description adds meaning beyond the schema by explaining each parameter's role in the workflow (e.g., 'saved_site_id (required integer, from save_site or list_saved_sites)'), providing default values, and including a concrete example. This additional context justifies the higher score.

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 clearly states the tool's purpose: 'Arm an email watch on a site you already saved'. It uses a specific verb-resource combination and distinguishes itself from siblings like set_market_alert (for markets) and save_site (for saving new sites), making its scope unambiguous.

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?

The description provides explicit when-to-use guidance (after save_site), when-not-to-use ('Do NOT use to watch a whole MARKET... or to save a new site'), and prerequisites (call bind_email first on free tier). It also names alternatives (set_market_alert, save_site) and offers concrete workflow steps.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/azmartone67/dchub-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server