Skip to main content
Glama
Grafana MCP Server
by nks1097

grafana_gerar_relatorio_desempenho

Generate Grafana performance reports covering query latency and resource consumption for a selected dashboard and time period in PDF or other formats.

Instructions

  1. Gerar relatório de desempenho, latência de consultas e consumo de recursos.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "grafana_gerar_relatorio_desempenho"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatoNopdf
periodoNo24h
dashboard_uidNo

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.4/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 says whether the tool is read-only, triggers generation jobs, or where the report goes. It only names the subject matter of the report, which is purpose rather than behavior.

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?

It is a single short sentence with no padding, but the leading '73.' index is meaningless noise and the terseness comes at the cost of substance rather than being earned conciseness.

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?

An output schema exists, so return values need not be described, but a zero-annotation, zero-coverage three-parameter generation tool needs far more than one sentence: no scope, no permissions, no format/period semantics are given. The definition is not sufficient for an agent to call the tool confidently.

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?

Schema description coverage is 0% across three parameters (formato, periodo, dashboard_uid) whose titles reveal almost nothing — e.g. accepted format values and period syntax are entirely undocumented. The description mentions none of these parameters, so an agent gains no semantics beyond the bare titles.

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 clear verb ('Gerar') and resource ('relatório de desempenho') and lists the report's content scope (query latency, resource consumption), which is more specific than a bare name restatement. However, it does nothing to separate itself from the many sibling report tools (relatorio_executivo, disponibilidade, capacidade, incidentes), so an agent cannot tell which report to pick from the description alone.

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 performance report versus the five other report generators or the export tools (exportar_relatorio_pdf, exportar_relatorio_csv_excel). The content list implies the topic but never states a condition of use or an alternative.

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