Skip to main content
Glama

metrics_alerts

Retrieve all Prometheus alerting rules and their current state—firing, pending, or inactive—optionally filtered by state or backend target, so you can quickly assess active incidents.

Instructions

Get all Prometheus alerting rules and their current state (firing, pending, inactive).

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": "metrics_alerts"
  }
}

Input Schema

NameRequiredDescriptionDefault
filterNoFilter alerts by stateall
targetNoNamed backend instance to query (configured: default). Defaults to the primary.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.8.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. The word 'Get' implies a read-only operation and the parenthetical identifies the state vocabulary returned, but there is nothing about permissions, rate limits, result size, pagination, or what each alert entry contains.

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 with zero filler; the resource comes first and the state enumeration is a useful qualifier rather than padding.

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?

For a simple two-optional-parameter read tool with no output schema, the description conveys the resource and the returned state dimension adequately. The remaining gap, return shape and volume, is modest given the tool's low complexity.

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 both 'filter' and 'target' are already documented in the schema, including the enum values and default. The description's enumeration of states mildly reinforces the filter vocabulary but adds no meaning beyond the structured fields.

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 states a specific verb and resource ('Get all Prometheus alerting rules') and enumerates the possible states it reports (firing, pending, inactive). That is enough to separate it from the query/target sibling tools, though it never explicitly names those alternatives.

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 only implied: an agent can infer this is the tool for alert-rule inventory and state, but there is no explicit when-to-use framing, no mention of when to prefer metrics_query or metrics_targets, and no statement about prerequisites such as a reachable backend.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.