Skip to main content
Glama
Grafana MCP Server
by nks1097

grafana_excluir_regra_alerta

Deletes a Grafana alert rule, requiring two-step approval to prevent accidental removal.

Instructions

  1. Excluir uma regra de alerta (Ação destrutiva - requer aprovação em dois passos).

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": {
      "uid_regra": "<uid_regra>"
    },
    "name": "grafana_excluir_regra_alerta"
  }
}

Input Schema

NameRequiredDescriptionDefault
uid_regraYes
token_aprovacaoNo

Output Schema

NameRequiredDescriptionDefault
erroNoMensagem de erro amigável caso haja falha
dadosNoCarga útil da resposta estruturada
avisosNoLista de alertas e avisos operacionais
sucessoNoIndica se a operação foi bem-sucedida
metadadosNoMetadados da execução
id_requisicaoNoIdentificador único da operação

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description does carry useful behavioral context: it declares the operation destructive and discloses a two-step approval requirement. However, it omits irreversibility, permission requirements, and what exactly is deleted beyond 'the rule', leaving meaningful 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.

Conciseness4/5

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

A single efficient sentence that front-loads the action. The stray '55.' numbering adds minor noise but the sentence otherwise earns its place.

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 tool with no annotations and 0% schema description coverage on a required identifier, the description is too thin. An output schema exists so return values needn't be explained, but the parameter semantics gap and missing permissions/irreversibility context leave the agent under-informed.

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?

Schema coverage is 0% and the description explains neither parameter. The phrase 'requer aprovação em dois passos' hints at the token_aprovacao parameter's purpose, but uid_regra (the required identifier) is entirely undocumented, and no format or source for it is given.

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 names a specific verb+resource: 'Excluir uma regra de alerta' (delete an alert rule). This clearly distinguishes it from sibling operations like criar/atualizar/obter/listar_regra_alerta. The leading '55.' is noise but the intent is unmistakable.

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?

It flags that this is a destructive action requiring two-step approval, which is meaningful context about how it must be invoked. However, it doesn't explicitly route the agent to alternatives (e.g., when to disable vs delete a rule) or state prerequisites like permissions.

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

Deploy Server

Other Tools