Skip to main content
Glama
Grafana MCP Server
by nks1097

grafana_diagnosticar_degradacao

Diagnoses the probable root cause of service degradation using telemetry evidence and a reported symptom, helping teams identify where to investigate first.

Instructions

  1. Diagnosticar a causa raiz provável de degradação com base em evidências de telemetria.

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": {
      "nome_servico": "<nome_servico>",
      "sintoma_relatado": "<sintoma_relatado>"
    },
    "name": "grafana_diagnosticar_degradacao"
  }
}

Input Schema

NameRequiredDescriptionDefault
nome_servicoYes
sintoma_relatadoYes

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.7/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 burden. It does not disclose which telemetry sources are consulted, whether it is read-only, how long such a cross-signal diagnosis takes, or what confidence/reasoning the result carries beyond the mere existence of an output schema.

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 core action. The stray '49.' numbering prefix is noise, but nothing else is wasted.

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?

The output schema covers return values, but for a complex cross-signal diagnostic tool with no annotations and two entirely undocumented parameters, the definition leaves too much for the agent to guess about inputs and behavior.

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%, yet the description adds nothing about the two required parameters. It does not clarify the expected format of nome_servico (service name, ID, qualified path) nor what granularity or phrasing sintoma_relatado should have, which is essential for a diagnosis tool.

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: diagnose the probable root cause of degradation from telemetry evidence. This clearly differs from sibling CRUD tools and from narrower diagnostics like grafana_diagnosticar_alertas or grafana_diagnosticar_fontes_dados, though the description does not explicitly name those distinctions.

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?

No guidance on when to use this instead of the closely overlapping siblings grafana_investigar_servico, grafana_correlacionar_logs_metricas_traces, or grafana_detectar_anomalias_metricas. The agent must infer the selection criteria from tool names alone.

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