Skip to main content
Glama
mshegolev

mshegolev/prometheus-mcp

alertmanager_list_alert_groups

Read-onlyIdempotent

List alert groups from Alertmanager to see how alerts are grouped for notification, including labels, receiver, and alert count.

Instructions

List alert groups from Alertmanager showing routing topology.

Wraps GET /api/v2/alerts/groups. Returns groups with their labels, receiver, and alert count — shows how alerts are grouped for notification.

Examples: - Use when: "Why did I get one notification instead of many?" → check which alerts are in the same group. - Use when: "What receiver handles payment alerts?" → find the group and check its receiver. - Don't use when: You want individual alert details (call alertmanager_list_alerts).

Returns: dict with total_groups / total_alerts / groups (list with labels, receiver, alert_count).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
instanceNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
groupsYes
total_alertsYes
total_groupsYes
Behavior4/5

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

Annotations already indicate read-only, idempotent, non-destructive. Description adds context about wrapping a GET API endpoint and returning grouping logic with labels, receiver, and alert count, supplementing the annotations well.

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?

Efficiently structured with bullet points and examples, each sentence adds value without redundancy.

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?

Output schema existence is hinted, and description details the return structure. However, the undocumented parameter reduces completeness slightly.

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

Parameters2/5

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

Input schema has one optional parameter 'instance' with no description (0% coverage). The description does not mention or explain this parameter, leaving its purpose ambiguous.

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 clearly states it lists alert groups showing routing topology, and distinguishes from sibling tool alertmanager_list_alerts by specifying it returns grouped information rather than individual alerts.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit examples of when to use (e.g., checking grouping for notifications) and when not to use (when individual alert details needed), including a named alternative.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mshegolev/prometheus-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server