Skip to main content
Glama

get_execution_trace

Read-onlyIdempotent

Retrieve a hierarchical multi-agent execution trace from a root execution ID to inspect supervisor-to-sub-agent phases, tool calls, and per-node costs.

Instructions

Hierarchical multi-agent execution trace from a root_execution_id: supervisor→sub-agents with phases, tool calls and cost per node

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": {
      "root_execution_id": "<root_execution_id>"
    },
    "name": "get_execution_trace"
  }
}

Input Schema

NameRequiredDescriptionDefault
root_execution_idYesRoot execution UUID (root_execution_id)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.4
    • changedInput schema / properties / root_execution_id / description
      Previous value: -"UUID da execução raiz (root_execution_id)"New value: +"Root execution UUID (root_execution_id)"
  2. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. What the description adds beyond that is return-shape context — hierarchy, phases, per-node tool calls and cost — which is useful given there is no output schema. It says nothing about behavior when the root execution ID is unknown, about trace depth/size limits, or about latency, so the addition is modest.

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?

One compact sentence with the return contents front-loaded and no filler. It reads as a noun phrase rather than a sentence, which slightly weakens the framing of what the tool actually does, but nothing is wasted.

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?

With no output schema, the description carries the burden of telling an agent what comes back, and it does list phases, tool calls and cost per node. However, for a potentially large hierarchical trace it omits depth bounds, size or truncation behavior, and error behavior for an invalid or non-root ID, leaving meaningful gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the single parameter is already documented as the root execution UUID. The description does reinforce that the value must be a *root* execution rather than a sub-agent or child execution ID, which is a small semantic addition. Otherwise it adds no format, validation, or example detail.

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 resource (hierarchical multi-agent execution trace) and states what it contains (supervisor→sub-agents with phases, tool calls, cost per node), which is far more informative than the bare name. It stops short of explicitly distinguishing itself from nearby siblings such as get_execution_diagnostics, get_process_trail or get_session_agent_tree, so an agent must infer the boundary.

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 guidance, no preconditions, and no mention of an alternative tool for related trace or diagnostic needs. The phrase 'from a root_execution_id' implies the preconditions but never states them as guidance.

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