Skip to main content
Glama
ntk148v

alertmanager-mcp-server

delete_silence

Remove a specific alert silence by its ID to restore notifications in Alertmanager.

Instructions

Delete a silence by its ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
silence_idYes

Implementation Reference

  • The delete_silence tool handler: an async function that deletes a silence by ID via DELETE request to Alertmanager API /api/v2/silences/{silence_id}, using make_request helper.
    @mcp.tool(description="Delete a silence by its ID")
    async def delete_silence(silence_id: str):
        """Delete a silence by its ID
    
        Parameters
        ----------
        silence_id : str
            The ID of the silence to be deleted.
    
        Returns
        -------
        dict:
            The response from the Alertmanager API.
        """
        return make_request(
            method="DELETE", route=url_join("/api/v2/silences/", silence_id)
        )
  • MCP tool registration decorator for delete_silence.
    @mcp.tool(description="Delete a silence by its ID")
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Delete' implies a destructive operation, the description doesn't mention whether this action is reversible, what permissions are required, what happens to associated alerts, or what the response looks like. This leaves significant gaps for a mutation tool.

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?

The description is extremely concise with just five words, front-loading the essential information. Every word earns its place, making it easy to parse quickly without unnecessary elaboration.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive operation with no annotations, no output schema, and minimal parameter documentation, the description is insufficient. It doesn't address critical questions like what happens after deletion, error conditions, or how this tool relates to the sibling tools in the alert management system.

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?

The schema has 0% description coverage, but the description adds minimal value by mentioning the parameter ('silence_id') in context. However, it doesn't explain what format the ID should be, where to find it, or provide any examples. For a single parameter tool with no schema documentation, this is barely adequate.

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 clearly states the action ('Delete') and target resource ('a silence by its ID'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its sibling 'get_silence' or explain what a 'silence' is in this context, which prevents a perfect score.

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

Usage Guidelines2/5

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

No guidance is provided about when to use this tool versus alternatives like 'post_silence' (which likely creates silences) or 'get_silence' (which retrieves them). The description only states what the tool does, not when it's appropriate to call it.

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/ntk148v/alertmanager-mcp-server'

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