Skip to main content
Glama

ai_modeling_canvas_run_get

Read-only

Inspect a single Canvas execution by run ID to review its status, results, and errors.

Instructions

Inspect one Canvas execution.

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": {
      "runId": "<runId>"
    },
    "name": "ai_modeling_canvas_run_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
runIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds nothing beyond that: no indication of what state a run must be in, whether the response is a snapshot or streamed, or how to handle an unknown or expired runId.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The sentence is short and front-loaded with no wasted words, which is good. But the brevity comes at the cost of substance, leaving the definition under-specified rather than efficiently scoped.

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

Completeness2/5

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

With no output schema and only three annotation hints, the description carries the burden of explaining return content for a retrieval tool and does not. An agent knows it inspects a run but not what it gets back or how to use it.

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

Parameters2/5

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

The single runId parameter has 0% schema description coverage and a constrained pattern but no stated meaning. The description does not explain what a runId is, where it is obtained, or what happens when it is invalid, so it fails to compensate for the coverage gap.

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

Purpose3/5

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

"Inspect one Canvas execution" names a verb and a resource and signals singular scope, which separates it from list-style siblings. However, "inspect" is vague about what is actually retrieved, and nothing distinguishes it from ai_modeling_canvas_run_check or ai_modeling_canvas_events.

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 mention of prerequisites, and no routing to alternatives such as run_check for status polling or events for history. The agent must infer the selection from sibling names alone.

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