Skip to main content
Glama

List alert rules

list_alerts
Read-onlyIdempotent

Named alerts on this account. Each row has name, id, alreadyOnThis (every match except dismissed, including pending review), pendingReview, and filters (a place list longer than 25 is summarised in placesSummary; get_alert has the full filters). Does not use credits. get_alert_matches reads the projects on one alert. Supports limit and offset.

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_alerts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoAlerts per page. Free — config rows, not records.
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds two genuinely useful behaviours beyond that: no credit consumption, and truncation of long place lists into placesSummary with get_alert as the escape hatch. It does not discuss ordering, defaults for limit/offset, or total-count behaviour.

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?

Front-loaded with the resource and its fields before the routing notes, and every clause carries information. The nested parenthetical about placesSummary is dense but earns its place.

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 field enumeration (name, id, alreadyOnThis, pendingReview, filters) is exactly what an agent needs and is supplied. Pagination and the summarisation caveat are covered; only offset semantics remain unstated, which is a minor gap for a two-parameter read tool.

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 50% — limit is documented in the schema, offset is not. The description only says "Supports limit and offset" without adding meaning for offset (or a default for limit), so it neither compensates for the gap nor adds much over 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?

Identifies the resource and scope ("Named alerts on this account") and enumerates the row fields, so the agent knows exactly what a call yields. It also explicitly distinguishes itself from get_alert (full filters) and get_alert_matches (projects on one alert), though the list verb itself is left implicit and only carried by the title.

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?

Names the alternatives and the condition that selects them: get_alert when full filters are needed, get_alert_matches when project-level matches are needed. It also flags the cost consideration ("Does not use credits"). There is no explicit statement of when not to use it, but the routing is clear.

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