Skip to main content
Glama

list_alert_rules

Read-onlyIdempotent

List this account's metric alert rules (cost, usage and event rules): the slice and condition each judges, how many series are firing now, and the plan's rule limit. Mirrors GET /api/accounts/:accountId/alert-rules.

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

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile is covered. The description adds real value beyond that by describing what each returned rule carries (the slice and condition it judges, current firing series count) plus the plan's rule limit, and by stating it mirrors a specific REST endpoint. It does not mention pagination or result-size behavior, which is the main remaining gap.

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?

A single front-loaded sentence identifies the verb and resource first, then enumerates return contents in a compact colon list, then closes with the REST mirror. There is no filler or repetition.

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 zero parameters and no output schema, the description carries the burden of telling the agent what comes back, and it does so concretely (slice, condition, firing count, plan rule limit). Only the absence of pagination/volume guidance keeps it from being fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes no parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. No parameter-level meaning is missing.

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?

States a specific verb ('List') and resource ('this account's metric alert rules') with an account-level scope, and the parenthetical 'cost, usage and event rules' narrows what kind of rules are returned, which helps separate it from siblings like list_alert_channels, list_alert_deliveries and list_alert_history. It stops short of naming any sibling as an alternative, so differentiation is inferential rather than explicit.

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?

Usage is implied by the resource and the account scope, but there is no explicit when-to-use statement, no exclusions, and no pointer to related tools such as the channels or history listings. An agent can guess this is the read path for rule definitions, but nothing confirms when it should be preferred over the other alert-* tools.

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