Skip to main content
Glama

Update a building permit alert

update_permit_alert
DestructiveIdempotent

Updates a building permit alert by its palr_ id. Only the fields passed change, and each one overwrites the previous setting for every member of a shared alert. Same fields and the same place rules as create_permit_alert; active:true turns a paused alert back on. Does not use credits. Editing the filters here makes the alert API-made, so its scheduled runs are charged from then on: each new or changed permit a run adds counts as one export record, or 1 credit on API Only and the trial. Say so before changing filters. Confirm with the user first.

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": "update_permit_alert"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo1–120 characters.
shareNoTeam sharing. Any member of a shared alert may read, edit, run and delete it. Sharing requires a paid plan.
activeNofalse pauses the alert.
alertIdYesThe permit alert's public id ("palr_…"), from list_permit_alerts or create_permit_alert.
cadenceNoHow often new matches are emailed: daily, weekly, or monthly.
filtersNoThe search_permits filter names as a JSON object, e.g. {"cities":["Lehi"],"workTypes":["pool"],"valueMin":50000}. Name a place (states, counties, or cities): at most 5 states and 25 counties or cities, unless the plan is nationwide, and inside the plan area. permitIds, contractorKeys, placeKey, and bbox cannot be saved on an alert.
findContactInfoNotrue runs Find Contact Info on each run's new permits, up to 200 a run: 1 credit per permit only when it adds an email, phone, or personal LinkedIn profile the permit did not print. Homeowners are never looked up. Confirm with the user before turning it on.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Goes well past the annotations (readOnlyHint=false, destructiveHint=true, idempotentHint=true) by disclosing that each supplied field overwrites the prior setting for every member of a shared alert, that updating itself spends no credits, and that editing filters flips the alert to API-made so future scheduled runs bill 1 credit per added permit.

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 identity and partial-update semantics, then cost and confirmation warnings — the highest-risk information is early. The credit sentence is long and dense, but each sentence carries distinct operational information.

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?

For a 7-parameter destructive mutation with no output schema, it covers overwrite behavior, shared-alert impact, resume semantics, and billing side effects. It does not indicate what the call returns, which is the only notable gap for an agent verifying success.

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 the baseline is 3, but the description adds meaning the schema does not: active:true specifically re-enables a paused alert, and filter edits carry a billing consequence and confirmation requirement. Place-rule details are largely duplicated from the schema's filters description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (updates) and resource (a building permit alert) plus its id prefix 'palr_', and anchors field semantics to create_permit_alert. It never names the sibling 'update_alert', so the agent is not explicitly told how this differs from the non-permit alert updater.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete operating conditions: use it to change only the fields passed, use active:true to resume a paused alert, and 'Confirm with the user first' / 'Say so before changing filters' before cost-incurring edits. It lacks an explicit when-not-to-use statement versus create_permit_alert or preview/run siblings.

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