Skip to main content
Glama

Run an alert now

run_alert
Destructive

Starts an alert run now. It emails the digest to members and to any saved extra addresses, and POSTs a saved webhook. Those sends cannot be unsent. Does not use credits to start; the run charges when it delivers records. preview_alert returns the match count and credit quote for that run. get_alert_matches reads projects already on the alert. A repeat in the same window returns already_running and adds no charge. Manual runs are capped at 3 per America/Denver calendar day.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "alertId": "<alertId>"
    },
    "name": "run_alert"
  }
}

Input Schema

NameRequiredDescriptionDefault
alertIdYesThe planned-project alert's public id ("alr_…"), from list_alerts or create_alert. Permit alert ids ("palr_…") go to the permit alert tools.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations: names the side effects (email digest to members and saved extra addresses, POST to saved webhook), states they cannot be unsent, and explains the credit model (no charge to start, charged on delivery). The already_running short-circuit and the daily cap add real operational context the destructiveHint/openWorldHint flags alone would not convey.

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?

Six short sentences, front-loaded with the action and its irreversible consequence, then progressively the credit semantics, siblings, and limits. Nothing is redundant or padded.

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 destructive, open-world, non-idempotent mutation with no output schema, the description covers side effects, irreversibility, cost timing, dedupe behavior, and rate limits. An agent has everything needed to call it correctly or divert to preview_alert.

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

Parameters3/5

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

Only one parameter, alertId, and the schema already documents it at 100% coverage including the alr_/palr_ distinction and the pointer to permit alert tools. The description adds no further parameter-level meaning, so the baseline of 3 applies.

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?

Opens with a specific verb and resource ("Starts an alert run now") and immediately situates it against siblings preview_alert and get_alert_matches. An agent can tell this apart from the read-only siblings without opening any 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?

Explicitly routes to alternatives: preview_alert for match count and credit quote, get_alert_matches for already-matched projects. It also states what happens on a repeat inside the same window (already_running, no charge) and the 3-per-day cap, which are the key conditions for deciding whether to call it.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources