Skip to main content
Glama
comqx

Prometheus Alertmanager MCP Server

by comqx

delete-silence

Remove a specific silence from Prometheus Alertmanager to resume alert notifications. Provide the silence ID to delete it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
silenceIdYesID of the silence to delete

Implementation Reference

  • The handler function that implements the delete-silence tool logic. It sends a DELETE request to the Alertmanager API to delete the specified silence and returns success or error message.
        try {
          // Delete the silence
          await fetchFromAlertmanager(`silence/${silenceId}`, {
            method: 'DELETE',
          });
          
          return {
            content: [{
              type: "text",
              text: `Successfully deleted silence with ID: ${silenceId}`
            }]
          };
        } catch (error: unknown) {
          const errorMessage = error instanceof Error ? error.message : String(error);
          return {
            content: [{
              type: "text",
              text: `Error deleting silence: ${errorMessage}`
            }],
            isError: true
          };
        }
      }
    );
  • Input schema for the delete-silence tool, defining the silenceId parameter using Zod.
      silenceId: z.string().describe("ID of the silence to delete"),
    },
  • src/index.ts:319-348 (registration)
    Registration of the delete-silence tool on the MCP server using server.tool(), including schema and handler.
      "delete-silence",
      {
        silenceId: z.string().describe("ID of the silence to delete"),
      },
      async ({ silenceId }) => {
        try {
          // Delete the silence
          await fetchFromAlertmanager(`silence/${silenceId}`, {
            method: 'DELETE',
          });
          
          return {
            content: [{
              type: "text",
              text: `Successfully deleted silence with ID: ${silenceId}`
            }]
          };
        } catch (error: unknown) {
          const errorMessage = error instanceof Error ? error.message : String(error);
          return {
            content: [{
              type: "text",
              text: `Error deleting silence: ${errorMessage}`
            }],
            isError: true
          };
        }
      }
    );
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

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