Skip to main content
Glama
Grafana MCP Server
by nks1097

grafana_obter_painel

Fetches the configuration and queries for a specific dashboard panel by dashboard UID and panel ID, enabling inspection or reuse of panel definitions.

Instructions

  1. Recuperar a configuração e consultas de 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_obter_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.8/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. 'Recuperar' implies a non-destructive read and it names the returned content (config + queries), but it discloses nothing about permissions, error behavior, or side effects. An output schema exists, which lightens the return-value burden, but the read/mutation and access profile remain unstated.

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, front-loaded sentence that wastes no words. The only flaw is the stray enumerator '4.' at the start, which is minor noise but not harmful.

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

Completeness3/5

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

An output schema exists, so return values are covered, and the tool has only two parameters, keeping inherent complexity low. However, with no annotations and 0% schema description coverage, the description leaves the agent without parameter semantics or usage context, making it only minimally viable.

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%, and both parameters (id_painel integer, uid_dashboard string) are undocumented. The description implies a dashboard identifier plus a panel identifier, which loosely maps to the two params, but it never clarifies the uid-vs-id distinction or how to obtain id_painel, so the coverage gap is not compensated.

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 states a specific verb (recuperar) and resource (configuração e consultas de um painel), scoped to a single panel within a dashboard, which distinguishes it from the whole-dashboard siblings like grafana_obter_dashboard. The stray leading '4.' is odd but does not obscure intent. It stops short of explicitly routing against near neighbors such as grafana_gerenciar_consultas_painel or grafana_executar_consulta_painel.

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?

The description only says what the tool retrieves; it gives no when-to-use guidance, no prerequisites, and no mention of alternatives like grafana_obter_dashboard or grafana_executar_consulta_painel. An agent must infer the use case entirely.

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