Skip to main content
Glama

ai_modeling_canvas_batches

Read-only

Lists result batches for a Canvas node so you can inspect and manage generated outputs.

Instructions

List result batches for a Canvas node.

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": {
      "nodeId": "<nodeId>"
    },
    "name": "ai_modeling_canvas_batches"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

C2.7/5.0
Behavior2/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. The description adds nothing beyond that: no ordering, pagination, recency, or retention behavior for batches, and no indication of what a 'result batch' contains or whether empty results are possible.

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 front-loaded sentence with zero filler, but the brevity comes at the cost of missing operational detail rather than reflecting genuine economy.

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?

For a one-parameter, no-output-schema list tool the description could still state what a batch is, how many are typically returned, and how to proceed to batch_select. None of that is present, so the agent is left to guess at the return shape and next step.

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 burden for nodeId. It only implies the parameter by saying 'for a Canvas node' — it never states the identifier format, where to obtain a valid nodeId, or what happens if the node has no batches.

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 gives a specific verb and resource ('List result batches') scoped to 'a Canvas node', so the agent knows exactly what is returned. It does not distinguish this from siblings like ai_modeling_canvas_batch_select, which likely operates on a single batch, leaving the list-vs-select distinction implicit.

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 stated prerequisite such as first obtaining a nodeId from ai_modeling_canvas_get, and no mention of the natural follow-up tool (batch_select). The agent must infer the entire workflow from the name 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