Skip to main content
Glama

ai_modeling_canvas_run_check

Read-only

Validates native Canvas run preconditions for selected nodes before execution, letting agents detect blocking issues without creating a run.

Instructions

Check the native Canvas run preconditions for selected nodes without creating a run.

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>",
      "nodeIds": "<nodeIds>"
    },
    "name": "ai_modeling_canvas_run_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeIdsYes
canvasIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description usefully confirms the non-mutating nature ('without creating a run'), but adds nothing about what happens when preconditions fail, whether errors are returned or reported as data, or how exhaustive the check is.

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?

A single well-formed sentence with the action front-loaded and the non-mutating constraint placed where it matters. Nothing is wasted, though the term 'native Canvas run preconditions' is left undefined and does more naming than explaining.

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?

With no output schema and 0% parameter description coverage, the description should say what a check yields (a pass/fail verdict, a list of unmet preconditions, or an error) and what 'preconditions' encompasses. It leaves both unanswered for a validation tool whose entire value is its verdict.

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, yet it only gestures at the two parameters through the phrases 'Canvas' and 'selected nodes.' It adds no meaning about canvasId format, the 1-100 nodeIds bounds, or the allowed id pattern, all of which an agent must discover from the raw schema.

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 states a specific verb-resource pair: 'Check the native Canvas run preconditions for selected nodes,' and the trailing clause 'without creating a run' implicitly separates it from the sibling ai_modeling_canvas_run. It is clear what the tool does without needing to open the schema, though it never names the sibling it contrasts with.

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 only implied: an agent can infer this is a pre-flight validation step before calling a run tool, reinforced by 'without creating a run.' There is no explicit statement of when to prefer this over actually running, nor any prerequisite or exclusion guidance.

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