Skip to main content
Glama

Get execution details

get_execution_details
Read-only

Get full details for a specific execution including all steps, their statuses, and error excerpts. Use this when you have an execution_id from list_recent_executions and need to drill into the failing step or sequence of operations. An execution is an organisation object: no cluster is needed to read one, and organisation-scoped executions (registry syncs, chart reads) have none.

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

Input Schema

NameRequiredDescriptionDefault
cluster_idYesAnkra cluster id (UUID) the call targets. Discover ids with list_clusters.
execution_idYesThe UUID of the execution to fetch.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

readOnlyHint=true already establishes the safety profile, so the useful addition here is scope information: executions are organisation objects and organisation-scoped runs (registry syncs, chart reads) have no cluster. That is genuinely non-obvious context. However, the claim 'no cluster is needed to read one' sits uneasily beside a schema that marks cluster_id as required, leaving the agent unsure of the actual preconditions.

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?

Three sentences, front-loaded with purpose then usage then scope, with no filler. The final scope sentence is dense but earns its place; only its ambiguous relationship to the required cluster_id slightly weakens an otherwise tight definition.

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?

There is no output schema, so the description carries the burden of describing the return shape (steps, statuses, error excerpts) and does so. For a read-only, two-parameter diagnostic tool that is nearly complete; the unresolved cluster_id expectation is the one loose end an agent would want settled.

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 coverage is 100%, so both parameters are already documented and the baseline is 3. The description usefully adds provenance for execution_id (obtained from list_recent_executions), but its statement that no cluster is needed directly conflicts with cluster_id being a required field, which muddies rather than clarifies that parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource ('Get full details for a specific execution') and enumerates what the payload contains (all steps, their statuses, error excerpts), which cleanly separates it from list_recent_executions and from aggregate siblings like get_execution_trends.

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

Usage Guidelines4/5

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

Explicitly states the entry condition ('when you have an execution_id from list_recent_executions') and the intent ('drill into the failing step'), which is exactly the routing information an agent needs. It gives no explicit 'do not use for X' exclusion against nearby tools such as get_execution_trends or wait_for_execution, so it stops short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.