Skip to main content
Glama
Grafana MCP Server
by nks1097

grafana_obter_detalhes_trace

Retrieve the span tree, duration, and metadata for a distributed Tempo trace to inspect request flow and diagnose latency issues.

Instructions

  1. Recuperar a árvore de spans, duração e metadados de um trace distribuído no Tempo.

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": {
      "trace_id": "<trace_id>"
    },
    "name": "grafana_obter_detalhes_trace"
  }
}

Input Schema

NameRequiredDescriptionDefault
trace_idYes
datasource_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.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 disclosure burden and does little with it. 'Recuperar' implies a read, but there is no mention of permission needs, datasource resolution behavior, what happens if the trace ID is unknown, or any scoping/limits.

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 nothing beyond the meaningless '44.' numbering prefix. Size is appropriate for the amount of information conveyed.

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 structure needn't be described. However, for a two-parameter tool with zero schema coverage and no annotations, the description should still clarify the datasource_uid default and trace_id format, which it omits.

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?

Two parameters with 0% schema description coverage: neither trace_id nor datasource_uid is explained in the schema. The description only hints that the trace lives in Tempo, which loosely gestures at datasource_uid, but gives no format for trace_id or what happens when datasource_uid is omitted (default null).

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?

Specific verb+resource: retrieves the span tree, duration and metadata of a distributed trace in Tempo. An agent can tell this is the trace-detail fetch rather than a listing or query. It stops short of a 5 because nothing distinguishes it from close siblings like grafana_consultar_tempo or grafana_explorar_atributos_trace, and the stray '44.' prefix adds noise.

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 statement of when to use this versus grafana_consultar_tempo, grafana_comparar_traces or grafana_explorar_atributos_trace, and no prerequisites such as needing a Tempo datasource. Usage must be inferred entirely from the name and the word 'trace'.

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