Skip to main content
Glama

ai_modeling_canvas_run

Run selected Canvas nodes with explicit inputs and a checked graph revision. Use a stable request_id so safe retries reuse the original job and avoid conflicting reruns.

Instructions

run selected Canvas nodes with explicit inputs and a checked graph revision. Uses your Studio account and a stable request_id. Reuse returns the original job; changed input conflicts; outcome_unknown must never be blindly retried.

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": {
      "request_id": "<request_id>",
      "max_estimated_credits": "<max_estimated_credits>",
      "parameters": "<parameters>"
    },
    "name": "ai_modeling_canvas_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
parametersYes
request_idYes
max_estimated_creditsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

B3.4/5.0
Behavior4/5

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

Annotations declare a non-read-only, open-world, non-destructive operation, and the description adds genuinely non-derivable behavior: requests authenticate against the Studio account, request_id makes calls idempotent (reuse returns the original job), changed inputs conflict, and an outcome_unknown state must not be blindly retried. That retry-safety warning is high-value context annotations cannot express; only job lifetime and credit-consumption behavior are left unstated.

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 dense sentences, front-loaded with the operation and followed by contract details; nothing is padding. It loses a point because phrases like 'explicit inputs' and 'checked graph revision' are compressed to the point of ambiguity for a first-time caller.

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

Completeness3/5

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

For a nested-parameter, three-required-field mutation with no output schema, the description covers idempotency, auth, and conflict/outcome_unknown semantics reasonably well. It does not cover the credit budget parameter's effect, the action modes, or what a successful response contains, leaving material gaps for an execution tool.

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?

Schema description coverage is 0%, so the description carries the full burden, but it only partially delivers: request_id is explained via reuse/conflict semantics and revision as 'checked'. The required max_estimated_credits budget (and what happens when it is exceeded) and the action enum values (generate/regenerate/retry/detect) are never explained, and 'explicit inputs' is too vague to clarify node_ids or parts.

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: run selected Canvas nodes, scoped to explicit inputs and a checked graph revision. An agent can infer this is the execution tool versus sibling read/poll helpers like canvas_run_check and canvas_run_get, 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 Guidelines3/5

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

Usage is implied rather than stated: 'checked graph revision' hints that you validate first and 'stable request_id' hints at idempotent retry, but the description never says when to prefer canvas_run_check, canvas_run_get, or canvas_run_stop. No explicit when-not guidance is given.

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