Skip to main content
Glama
Grafana MCP Server
by nks1097

grafana_investigar_servico

Investigate a service's health, error rate, latency, and dependencies to diagnose issues and target root causes.

Instructions

  1. Realizar uma investigação abrangente de saúde, taxa de erro, latência e dependências de um serviço.

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>"
    },
    "name": "grafana_investigar_servico"
  }
}

Input Schema

NameRequiredDescriptionDefault
nome_servicoYes

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 exist, so the description carries the full disclosure burden and largely drops it. It never says the operation is read-only, which data sources or time window it queries, whether it fans out across Prometheus/Loki/traces, or whether it can be slow or expensive. Only the broad 'what is measured' is disclosed.

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?

One front-loaded sentence with no filler, but it opens with a stray list artifact ('48.') that is noise to an agent, and the single sentence is thin for the amount of behavior left unexplained.

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 need not be described, and the one required parameter is at least named in the description's subject matter. However, for a multi-signal aggregate investigation with no annotations and no parameter documentation, the absence of any scope statement (time range, data sources, read-only nature) leaves real gaps.

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?

There is one parameter (nome_servico) with 0% schema description coverage, so the description must compensate and does not. It never explains the expected identifier form (job name, service label, namespace-qualified name) or matching behavior, which is exactly the ambiguity that causes failed invocations.

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 (investigar) plus a specific scope: health, error rate, latency, and dependencies of a service. That is materially more informative than a tautology and distinguishes it from narrow siblings like grafana_identificar_requisicoes_lentas or grafana_diagnosticar_degradacao. It stops short of a 5 because it never references any sibling or states what makes this the 'abrangente' choice.

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 when-to-use, when-not-to-use, or alternative routing. An agent facing grafana_diagnosticar_degradacao, grafana_correlacionar_logs_metricas_traces, and this tool has no textual basis for choosing among them, only the implied 'investigate a service' framing.

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