Skip to main content
Glama

get_execution_diagnostics

Read-onlyIdempotent

Retrieve diagnostics by execution_id or root_execution_id from chat_with_agent to inspect chronological model/tool calls, tokens, latency, finish_reason, cache reads/writes, caller correlation metadata.

Instructions

Get execution diagnostics: chronological model and tool calls, tokens, latency, model, finish_reason, cache reads/writes and caller correlation metadata. Use the execution_id or root_execution_id returned by chat_with_agent.

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": {
      "execution_id": "<execution_id>"
    },
    "name": "get_execution_diagnostics"
  }
}

Input Schema

NameRequiredDescriptionDefault
execution_idYesExecution UUID or root_execution_id returned by an agent invocation

Output Schema

NameRequiredDescriptionDefault
successNo
summaryNo
timelineNo
executionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.4
    • changedInput schema / properties / execution_id / description
      Previous value: -"UUID da execução (id do agent_executions ou root_execution_id)"New value: +"Execution UUID or root_execution_id returned by an agent invocation"
  2. Changed1 schema field changedv2.2.3
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "anyOf": [
      +    {
      +      "required": [
      +        "success",
      +        "execution"
      +      ]
      +    },
      +    {
      +      "properties": {
      +        "error": {
      +          "additionalProperties": true,
      +          "properties": {
      +            "code": {
      +              "type": "string"
      +            },
      +            "message": {
      +              "type": "string"
      +            }
      +          },
      +          "required": [
      +            "code",
      +            "message"
      +          ],
      +          "type": "object"
      +        },
      +        "success": {
      +          "const": false
      +        }
      +      },
      +      "required": [
      +        "success",
      +        "error"
      +      ],
      +      "type": "object"
      +    }
      +  ],
      +  "properties": {
      +    "execution": {
      +      "additionalProperties": true,
      +      "type": "object"
      +    },
      +    "success": {
      +      "type": "boolean"
      +    },
      +    "summary": {
      +      "additionalProperties": true,
      +      "type": "object"
      +    },
      +    "timeline": {
      +      "items": {
      +        "additionalProperties": true,
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "type": "object"
      +}
  3. First observedv0.1.0

TDQS

A3.6/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 without the description. The description adds the shape of the returned data (chronological ordering, cache reads/writes, caller correlation), though much of this is also carried by the output schema. No cost, rate-limit, or size/retention behavior 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences with no filler; the payload contents come first and the identifier-sourcing hint second. Every clause carries information and nothing is repeated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter, read-only lookup with an existing output schema, the description covers what an agent needs: what the diagnostics contain and where the ID comes from. The only real omission is disambiguation from similarly named trace/execution siblings.

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% and there is a single parameter whose description already states it accepts an Execution UUID or root_execution_id from an agent invocation. The description's note about sourcing the ID from chat_with_agent largely restates the schema, so it adds only marginal meaning beyond structured data.

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 gives a specific verb and resource ("Get execution diagnostics") and enumerates the concrete payload: chronological model and tool calls, tokens, latency, finish_reason, cache reads/writes, caller correlation metadata. That is far more than a restatement of the name. It stops short of distinguishing itself from the sibling get_execution_trace, which an agent could easily confuse with this diagnostics payload.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The second sentence tells the agent where the required identifier comes from ("execution_id or root_execution_id returned by chat_with_agent"), which is genuine invocation guidance. However, there is no when-to-use/when-not guidance and no mention of when to prefer get_execution_trace or get_trigger_execution instead.

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