Skip to main content
Glama
Grafana MCP Server
by nks1097

grafana_remover_painel

Remove a specific panel from a Grafana dashboard by specifying the dashboard UID and panel ID.

Instructions

  1. Remover um painel específico de um dashboard.

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_dashboard": "<uid_dashboard>",
      "id_painel": "<id_painel>"
    },
    "name": "grafana_remover_painel"
  }
}

Input Schema

NameRequiredDescriptionDefault
id_painelYes
uid_dashboardYes

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

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it never states that this is a destructive, irreversible mutation, whether permissions are required, or what happens to the surrounding dashboard layout. The presence of an output schema covers return values, but the risk profile is undisclosed.

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

Conciseness3/5

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

The single sentence is short, but the leading list numbering '15.' is noise, and the brevity comes at the cost of substance rather than from eliminating waste.

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 two-parameter mutation with zero annotation coverage and zero schema documentation, the definition leaves too much unstated: identifier formats, permissions, and irreversibility. Only the return value is covered, via the output schema.

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 description coverage is 0%, so the description must compensate and does not. It never explains that 'uid_dashboard' is the dashboard's unique identifier (not an ID or title) or that 'id_painel' is the numeric panel ID within that dashboard.

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?

States a specific verb+resource combination ('Remover um painel específico de um dashboard'), which clearly distinguishes it from siblings like grafana_excluir_dashboard (whole dashboard) and grafana_atualizar_painel (modify). It does not explicitly name those siblings, so it falls short of a 5.

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?

There is no guidance on when to use this versus grafana_atualizar_painel (which could also remove a panel by rewriting the panel list) or grafana_excluir_dashboard. No prerequisites, warnings, or conditions are stated.

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