Skip to main content
Glama

Get one alert

get_alert
Read-onlyIdempotent

One alert: alreadyOnThis, pendingReview, filters, cadence, and share roster. alreadyOnThis counts every match except dismissed, and pending review stays in that count. Does not use credits. get_alert_matches reads those projects.

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": "get_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

B3.4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, and closed-world behavior, so the description's job is lighter. It adds meaningful behavior beyond annotations: it says the call does not use credits and explains that alreadyOnThis counts matches except dismissed ones while pending-review matches remain counted.

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?

The description is short, front-loads the fields, and includes only useful notes about counting, credits, and get_alert_matches. Its telegraphic fragments make it slightly less clear than a fully formed sentence would be, but there is little wasted text.

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 simple one-parameter read tool with rich annotations and complete schema coverage, the description supplies the returned field list, counting semantics, credit behavior, and a pointer to get_alert_matches. It does not explain not-found behavior, but no output schema exists and the remaining gaps are minor.

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?

There is only one parameter and schema description coverage is 100%, with the schema explaining the alr_ public id source and the palr_ permit-id redirect. The description adds no parameter-level detail beyond that, so the schema does the work.

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

Purpose3/5

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

The description names the resource and lists returned fields (alreadyOnThis, pendingReview, filters, cadence, share roster), but it never states the action explicitly—'One alert' is a fragment rather than 'retrieves one alert.' It partly distinguishes from get_alert_matches by noting that sibling reads projects, but the core purpose remains inferred from the title/name.

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?

It implies this tool is for fetching alert metadata and that get_alert_matches is the alternative for projects, but it does not state when to use this versus list_alerts, get_alert_deliveries, or the permit alert tools. The schema carries the permit-id redirect, not the description.

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