Skip to main content
Glama

List your alerts

list_alerts
Read-onlyIdempotent

List saved alerts, newest first, with names, criteria, status and holds. Page with before.

Permission: alerts:read.

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
limitNoItems per page, 1–100. Default 50.
beforeNoCursor: pass next_before from the previous page to read older items.

Output Schema

NameRequiredDescriptionDefault
dataNo
next_beforeNo

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?

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description still adds value beyond them: result ordering (newest first), which fields come back, the cursor-based pagination contract, and the alerts:read permission requirement.

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?

Two short sentences plus a permission line, with the most load-bearing information (what it lists, ordering, pagination) front-loaded. Nothing is redundant or padded.

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 an output schema present, the description needn't explain return shape, and annotations cover the safety profile. It supplies permission, ordering and pagination, leaving only minor gaps such as filtering behavior or empty-result handling.

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% — limit's range/default and before's cursor semantics are fully documented in the schema. The description's "Page with before" restates rather than extends that, so the baseline 3 applies.

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?

The description gives a specific verb and resource ("List saved alerts") plus the ordering (newest first) and the fields surfaced (names, criteria, status, holds). It is clearly a listing tool distinct from the singular get_alert/edit_alert siblings, but it never explicitly contrasts itself with them, so it stops short of a 5.

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 tells the agent how to walk pages ("Page with before") and states the required permission (alerts:read), which is real operational guidance. It does not say when to reach for this versus get_alert or edit_alert, so usage 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