Skip to main content
Glama

Run a building permit alert now

run_permit_alert
Destructive

Runs a building permit alert now and emails the digest of new matches to its members. That email cannot be unsent. Does not use credits to start; the run is charged when it adds permits: each new or changed permit counts as one export record on County, State, and National, or 1 credit on API Only and the trial, whoever created the alert. Short of allowance, the run is refused whole with a quote and charges nothing. preview_permit_alert returns newSinceLastRun, the number the run would add; state that cost and run only after the user agrees. get_permit_alert_matches reads permits already on the alert, which is how to pull an alert; a permit this run charged for is not charged again there while it is unchanged. Manual runs are capped at 3 per 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_permit_alert"
  }
}

Input Schema

NameRequiredDescriptionDefault
alertIdYesThe permit alert's public id ("palr_…"), from list_permit_alerts or create_permit_alert.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the destructive/openWorld annotations: the email cannot be unsent, the run is charged only when it adds permits with per-target pricing differences, insufficient allowance refuses the whole run with a quote and no charge, and manual runs are capped at 3 per day. These are exactly the irreversibility, billing, and rate-limit facts an agent needs before a destructive call.

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-loads the action and the 'cannot be unsent' warning before cost semantics and alternatives, which is the right ordering. The pricing sentence is dense and slightly run-on, but each sentence carries decision-relevant information rather than filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description says what the run produces (new/changed permits counted as export records or credits) but does not describe the run response object itself. For a one-parameter destructive tool, the cost, refusal, and cap semantics make it largely complete.

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?

Schema coverage is 100% and the single alertId parameter is fully documented in the schema (public id 'palr_…', source tools list_permit_alerts and create_permit_alert). The description adds no parameter-level meaning beyond what structured data already provides, so the baseline 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?

A concrete verb-plus-resource statement — runs the alert now and emails the digest of new matches to members — plus immediate differentiation from preview_permit_alert (cost preview) and get_permit_alert_matches (pull existing permits). An agent can identify the operation and its side effect from the first sentence alone.

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?

Explicit sequencing: call preview_permit_alert to get newSinceLastRun, state that cost, and run only after the user agrees. It also names a distinct alternative (get_permit_alert_matches) for retrieving permits already on the alert, so when-to-use versus when-not-to-use is fully covered.

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