Skip to main content
Glama

List alerts

list_alerts
Read-only

List the organisation's alert definitions and their current firing state, with org-wide alert metrics (total/enabled/firing counts, triggers in the last 24h). Use this to answer questions about what alerts exist, which are firing, and their severity. Read-only. Optional filters: search (name substring), enabled (true/false), severity (critical/warning/info), resource_type, cluster_id.

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
pageNo1-based page number (default 1).
searchNoCase-insensitive substring match on the alert name.
enabledNoFilter to enabled (true) or disabled (false) alerts.
severityNoFilter by the alert's maximum rule severity.
page_sizeNoPage size (default 20, max 100).
cluster_idNoFilter to alerts whose rules target this cluster or apply to all clusters.
resource_typeNoFilter by the Kubernetes resource type the alert's rules target.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the "Read-only" sentence is largely redundant. The description still earns credit for disclosing what the response contains: alert definitions, current firing state, and org-wide metrics computed over a 24h window, which is context the annotations cannot express.

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 sentences, front-loaded with the resource and returned metrics before the use case and the filter summary. Some redundancy exists in the "Read-only" line and the filter recap that duplicates schema field descriptions.

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 description usefully covers what comes back (definitions, firing state, aggregate metrics). All seven params are optional and schema-documented, so the remaining gap is minor: nothing about paging behavior or result ordering/default sort.

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 the schema already documents all seven filters including the severity enum and page bounds. The description's filter list (search substring, enabled true/false, severity values, resource_type, cluster_id) mostly restates those field descriptions, adding no new syntax or semantics, so the baseline 3 applies.

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

Purpose5/5

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

The description pairs a specific verb and resource ("List the organisation's alert definitions and their current firing state") with the returned extras (org-wide total/enabled/firing counts and 24h triggers). That scope distinguishes it from siblings such as create_alert, set_alert_enabled, and list_alert_destinations without opening any schema.

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?

It gives an explicit use case: answering questions about which alerts exist, which are firing, and their severity. It does not name alternatives or exclusions (e.g., no pointer away from list_alertmanager_silences for silences), so the routing guidance is clear but incomplete.

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.