Skip to main content
Glama

Canvas Get Execution

aimixer_canvas_get_execution
Read-onlyIdempotent

Check an execution attempt by attempt_id, or recover a multi-node workflow by its project_id and request_id. May sync the stored status from the generation backend (at most once per 5 seconds per attempt); it never spends coins or starts jobs.

Input Schema

NameRequiredDescriptionDefault
attempt_idNo
project_idNo
request_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses that the call may sync stored status from the generation backend, quantifies the throttle (at most once per 5 seconds per attempt), and states the negative guarantee that no coins are spent and no jobs are started. That is exactly the kind of side-effect and rate-limit context annotations cannot convey.

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, zero filler. The primary lookup mode is front-loaded, the fallback mode follows, and the cost/rate caveats close it out.

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?

An output schema exists, so return values need no explanation, and the description covers both invocation modes, side effects, and throttling. The only meaningful omission is the origin/semantics of request_id, which an agent may not know how to obtain.

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

Parameters4/5

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

With 0% schema description coverage, the description carries the burden and does explain the oneOf semantics: attempt_id addresses a single attempt, while project_id and request_id together recover a multi-node workflow. It stops short of saying where request_id comes from or what format it takes, which leaves a gap for an undocumented parameter.

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?

States a specific verb and resource ('Check an execution attempt') plus a second distinct mode ('recover a multi-node workflow'). The agent can tell it is the read-side counterpart to start/stop/prepare execution, though no sibling is named explicitly.

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?

Gives the selection condition between the two modes (by attempt_id vs. by project_id + request_id) and implicitly excludes the start path with 'it never spends coins or starts jobs'. It does not name a specific alternative tool for launching or cancelling work, so the routing is clear but not fully spelled out.

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.

Resources