Skip to main content
Glama

Expire Alertmanager silence

expire_alertmanager_silence
Destructive

Expire (end) a silence in the cluster's Prometheus Alertmanager by its id, so the matching alerts resume notifying immediately. Find the id with list_alertmanager_silences or from the create_alertmanager_silence response. The Alertmanager service is auto-discovered; pass namespace/service/port only for non-standard installs.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "silence_id": "<silence_id>",
      "cluster_id": "<cluster_id>"
    },
    "name": "expire_alertmanager_silence"
  }
}

Input Schema

NameRequiredDescriptionDefault
portNoAlertmanager port (default 9093).
serviceNoAlertmanager Service name override (requires namespace).
namespaceNoNamespace to look for Alertmanager in (default: auto-discover across the cluster).
cluster_idYesAnkra cluster id (UUID) the call targets. Discover ids with list_clusters.
silence_idYesThe silence id (a UUID) to expire.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the safety profile is covered. The description adds real value by naming the consequence (alerts resume notifying immediately) and the auto-discovery default, but says nothing about whether the action is reversible/re-creatable or whether a repeat call on an already-expired id errors.

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 verb, action and effect; the id-discovery hint and the optional-override caveat each earn their place. Only minor redundancy between 'Expire (end)' and the effect clause keeps it off a 5.

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 and annotations carrying the safety signals, the description gives what an agent needs: the effect, the required id and its source, and when the optional targeting params matter. It leaves the success/return shape and failure behavior (already-expired id) implicit, which is a small gap for a mutation tool.

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 baseline is 3 and the schema already documents every parameter including defaults (9093, cluster-wide auto-discovery) and the UUID format. The description only reinforces the id's provenance and the conditional nature of namespace/service/port, adding modest meaning beyond the schema.

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?

States a specific verb and resource ('Expire (end) a silence in the cluster's Prometheus Alertmanager by its id') plus the observable effect ('matching alerts resume notifying immediately'), which cleanly separates it from create_alertmanager_silence and list_alertmanager_silences without opening either 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?

Explicitly routes the agent to where the required id comes from (list_alertmanager_silences or the create_alertmanager_silence response) and scopes the optional overrides ('pass namespace/service/port only for non-standard installs'). It stops short of stating when not to expire a silence or how to re-create one, so it is strong but not exhaustive.

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.