Skip to main content
Glama

List building permit alerts

list_permit_alerts
Read-onlyIdempotent

Building permit alerts on this account (ids start with "palr_"). Planned-project alerts are separate and list_alerts returns them. Each row has name, filters, cadence, sharing, and how many matches are pending review and kept. alertId returns one alert. get_permit_alert_matches reads the permits on an alert. Supports limit and offset. Does not use credits.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_permit_alerts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoAlerts per page. These are settings, not records.
offsetNo
alertIdNoReturn one permit alert ("palr_…") instead of the list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive, idempotent, closed-world behavior, so the safety bar is covered. The description adds genuinely new context: the row shape (name, filters, cadence, sharing, pending/kept match counts) and the cost note "Does not use credits", which an agent cannot get from annotations. It stops short of stating page-size defaults or total-count behavior.

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?

Dense, front-loaded sentences in fragments: identity, differentiation, row shape, single-fetch mode, pagination, cost. Nothing is padding, though the telegraphic style makes a couple of clauses ("how many matches are pending review and kept") read awkwardly on first pass.

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?

With no output schema, the description carries the return-value burden and does it: it enumerates the row fields and the pending/kept counts an agent needs to interpret results. Combined with pagination, cost, and sibling routing, nothing essential for a correct call is missing.

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?

At 67% schema coverage, the schema already documents alertId and limit; the description's "alertId returns one alert" largely restates the schema, and "Supports limit and offset" adds no syntax or bounds beyond maximum 100. The offset parameter remains undocumented in both places, so the description does not compensate for the remaining gap.

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?

States a concrete resource (building permit alerts on this account) and pairs it with the id prefix "palr_", plus explicitly separates it from planned-project alerts via list_alerts and from permit-level data via get_permit_alert_matches. An agent can distinguish it from the sibling alert tools without opening a 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: planned-project alerts go to list_alerts, permit-level reads go to get_permit_alert_matches, and a single alert is fetched here via alertId. That names both the alternatives and the conditions selecting them, leaving nothing to inference.

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