Skip to main content
Glama

get_trigger_execution

Read-onlyIdempotent

Retrieve a trigger execution and its recorded outcome by execution ID to troubleshoot failures.

Instructions

Retrieve one trigger execution and its recorded outcome for troubleshooting.

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_trigger_execution"
  }
}

Input Schema

NameRequiredDescriptionDefault
execution_idYesExecution UUID

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"New value: +"Execution UUID"
  2. 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 that a recorded outcome is returned, which is useful, but says nothing about behavior on a missing/invalid execution_id or about retention of old executions.

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?

The description is a single front-loaded sentence with no filler. It is efficient, though it leaves the troubleshooting rationale stated but undeveloped.

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

Completeness5/5

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

This is a low-complexity single-parameter read tool whose safety profile is already fully declared by annotations and whose only parameter is documented in the schema. There is no output schema, but the description states that the recorded outcome is returned, which is sufficient context for calling it correctly.

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?

There is only one parameter (execution_id), and schema description coverage is 100% ('Execution UUID'). The description adds no meaning beyond that: it does not explain how to obtain the ID or whether the ID format/scope matches list_trigger_executions, so the baseline of 3 applies.

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 and resource: 'Retrieve one trigger execution and its recorded outcome.' The singular scope plus the 'outcome' payload distinguishes it from list_trigger_executions by implication. However, it never names or contrasts against close siblings like get_execution_diagnostics or get_execution_trace, which cover overlapping troubleshooting territory.

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?

'for troubleshooting' implies a use case, but there is no explicit when-to-use vs when-not guidance and no reference to an alternative tool. An agent must infer on its own whether to call this instead of get_execution_trace or get_execution_diagnostics.

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