Skip to main content
Glama

Delete a building permit alert

delete_permit_alert
Destructive

Deletes a building permit alert for every member of a shared alert, not only the caller. Its matches and review decisions are removed. Only the owner may delete. Does not use credits. 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": "delete_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?

Beyond the destructive annotation, the description discloses important behavior: deletion affects every member of a shared alert, removes matches and review decisions, requires ownership, and does not use credits. These are material consequences that an agent would not know from the annotations alone.

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?

The description is short, front-loaded, and every sentence contributes useful information about scope, effects, authorization, credits, and confirmation. There is no wasted wording.

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, shared-alert deletion tool with no output schema, the description covers the important behavioral details an agent needs: shared scope, cascading removal, owner-only authorization, credit behavior, and user confirmation. It is complete enough to support correct selection and invocation.

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?

The input schema has 100% description coverage for the single alertId parameter, including its public id format and source. The description adds no additional parameter meaning, so the schema carries the full burden and the baseline of 3 is appropriate.

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 states a specific verb and resource: deleting a building permit alert. It also clarifies the scope as every member of a shared alert, not only the caller, which distinguishes it from a personal delete and from sibling tools like delete_alert.

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?

It gives clear usage constraints: only the owner may delete, and the user should be asked to confirm first. It does not explicitly name alternative tools or when-not-to-use conditions, but the owner restriction and confirmation requirement provide strong operational guidance.

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