Skip to main content
Glama

Price an alert run

preview_alert
Read-onlyIdempotent

Quote for an alert's next run, without running it. Uses the filters get_alert returns, including website-created map criteria. Returns matchCount, creditsRequired (export records on County, State, and National; credits on API Only and the trial), alreadyDeliveredUnchanged, and maxRecordsPerRun. Records this account already holds unchanged are not charged. 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>"
    },
    "name": "preview_alert"
  }
}

Input Schema

NameRequiredDescriptionDefault
alertIdYesThe planned-project alert's public id ("alr_…"), from list_alerts or create_alert. Permit alert ids ("palr_…") go to the permit alert tools.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety bar is low, yet the description still adds meaningful economics: which fields are returned, that already-delivered unchanged records are not charged, and which tiers bill export records versus credits. That pricing nuance is real value beyond the annotations, though it stops short of mentioning rate limits or error conditions on an invalid alert id.

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?

Six short sentences, front-loaded with the purpose and then the return fields, then the billing caveats. Nothing is redundant with the title or annotations.

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 compensates by enumerating the returned fields and explaining the credit model, which is what an agent needs to interpret the result. Minor gap: it does not say what happens for an unknown or permit-type alert id at call time.

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 alertId description already explains the alr_ prefix and the palr_ routing caveat, so the schema carries the parameter burden. The description's only addition is that the alert's filters come from get_alert, which is contextual rather than parameter-level detail, so baseline 3 fits.

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?

"Quote for an alert's next run, without running it" gives a specific verb and resource, and the 'without running it' clause cleanly separates it from run_alert. An agent can tell what it produces (a price estimate) without opening the schema.

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?

The 'without running it' phrasing plus 'Does not use credits' tells the agent exactly when to reach for this instead of an actual run, and it points at get_alert as the source of the filters it honors. It never explicitly names run_alert as the alternative for executing, so the routing is implied 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