Skip to main content
Glama

List alert rules

list_alert_rules
Read-only

This app's alert rules with their triggers, conditions, channels and throttles. defaults_active means no rule is enabled, so the built-in defaults listed there apply. Use it to see what will and won't alert.

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

Input Schema

NameRequiredDescriptionDefault
limitNoRows (default 50)
cursorNonext_cursor from the last answer

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description goes further by explaining the meaning of the defaults_active condition and by disclosing that each rule carries triggers, conditions, channels and throttles, which is real domain context. It stops short of describing pagination or response shape, which is a modest gap.

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?

Three short sentences, no padding, and the important caveat about defaults_active is placed before the usage sentence. The opening fragment is a noun phrase rather than a verb-led statement, which makes the first read slightly harder than it needs to be.

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?

There is no output schema, so the description usefully enumerates the main returned fields and explains the one non-obvious flag. For a two-parameter read-only listing tool that is close to sufficient; only pagination behavior is left uncovered.

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 description coverage is 100%, so limit and cursor are already documented in the schema. The description adds nothing about format, defaults, or cursor lifecycle, so 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 names the resource ("This app's alert rules") and enumerates what is returned (triggers, conditions, channels, throttles), which is more specific than the bare title. It does not explicitly contrast with the sibling list_error_alerts, so an agent must infer scope from the word "alert rules" alone.

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?

"Use it to see what will and won't alert" gives an implied purpose but no when-not-to-use guidance and no named alternative. The boundary with list_error_alerts is left entirely 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