Skip to main content
Glama

Keep or dismiss a permit on an alert

set_permit_alert_decision
Idempotent

Marks one building permit on a permit alert as kept (saved), dismissed, or pending (back to review). Decisions are per person: a teammate on a shared alert keeps their own. Repeating it changes nothing. Does not use credits.

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>",
      "permitId": "<permitId>",
      "decision": "<decision>"
    },
    "name": "set_permit_alert_decision"
  }
}

Input Schema

NameRequiredDescriptionDefault
alertIdYesThe permit alert's public id ("palr_…"), from list_permit_alerts or create_permit_alert.
decisionYessaved (kept), dismissed, or pending (back to review).
permitIdYesA permit id (permitId on a permit record).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Adds real context beyond the annotations: decisions are scoped per person even on a shared alert, and the call consumes no credits — neither is derivable from the hints. The 'repeating it changes nothing' line reinforces idempotentHint=true rather than contradicting it, and nothing conflicts with destructiveHint=false.

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?

Four short sentences, action and states front-loaded, then scope, idempotency, and cost as separate concerns. No filler or restated title.

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 three-parameter mutation with full annotation coverage and no output schema, this covers the non-obvious behaviors (per-user effect, idempotency, cost). Only minor gaps remain, such as whether authorization on a shared alert is required to change another person's state.

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 enum values (saved/dismissed/pending) are already documented in the schema, so the description's restatement of them adds little. alertId and permitId semantics come entirely from the schema.

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 (marks) plus the exact resource (one building permit on a permit alert) and enumerates the three resulting states. An agent can distinguish it from alert-level tools like dismiss_alert_project by the per-permit scope, though no sibling is named explicitly.

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

Usage Guidelines3/5

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

Gives useful framing (per-person decisions, idempotent, no credits) but never says when to choose this over alternatives such as remove_permit_from_list or the alert-level dismiss tools. Usage is implied by the scope sentence rather than stated.

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