Skip to main content
Glama

ai_modeling_canvas_runs

Read-only

List execution history for a specific Canvas to inspect past runs and track outcomes by providing its Canvas ID.

Instructions

List execution history for a Canvas.

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": {
      "canvasId": "<canvasId>"
    },
    "name": "ai_modeling_canvas_runs"
  }
}

Input Schema

NameRequiredDescriptionDefault
canvasIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered and the description is not obligated to restate it. The description contributes only that the tool returns a listing of past executions, saying nothing about ordering, recency, or result volume. That is a modest addition over the annotations, so a 3 fits.

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?

One front-loaded sentence with zero filler and no redundancy. It is efficient but borders on under-specification for a tool with no output schema, so it does not reach the top of the scale.

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?

This is a list tool with no output schema, no pagination hints, and no statement of what each history entry contains, so an agent cannot predict result size or shape before invoking it. Given that structured fields supply almost nothing and the description is a single clause, the definition is thinner than the tool's complexity warrants.

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?

With a single parameter at 0% schema description coverage, the description carries the burden of explaining canvasId, and it only implies that the value identifies a Canvas. It does not clarify whether the parameter expects an opaque ID, a name, or a path-like reference matching the schema pattern, nor whether an invalid value errors or returns empty.

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 uses a specific verb ('List') with a specific resource ('execution history') scoped to a Canvas, which is materially more informative than the bare tool name. It does not, however, distinguish itself from siblings that also surface runtime data such as ai_modeling_canvas_events or ai_modeling_canvas_lab_jobs, leaving the agent to infer the boundary.

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 or when-not-to-use guidance and no alternative is named. An agent cannot tell from this text whether to call this tool or ai_modeling_canvas_events when it wants run-related information about a canvas.

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