Skip to main content
Glama

ai_modeling_canvas_node_assets

Read-only

Lists results for selected Canvas nodes, enabling agents to inspect node outputs and manage associated assets in batch workflows.

Instructions

List results for selected Canvas nodes.

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

Input Schema

NameRequiredDescriptionDefault
nodeIdsYes

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=true, destructiveHint=false, and openWorldHint=true, so the description's only job is context beyond that. It adds nothing about the shape of the returned list, pagination, or the maxItems=100 cap defined in the schema.

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?

One short sentence is tightly written with no filler, but its brevity reflects under-specification rather than economy. The key noun 'results' is ambiguous given the tool name refers to assets.

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, one undocumented parameter, and no annotations beyond safety flags, the description leaves the return value and node-id semantics entirely unexplained. An agent cannot predict what it will get back or what a 'result' contains.

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% for the single required parameter nodeIds, so the description must compensate. 'Selected Canvas nodes' only weakly implies these are canvas node identifiers; nothing explains the accepted identifier pattern, the 1-100 range, or behavior for mixed valid/invalid ids.

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?

The description pairs a verb ('List') with a vague resource ('results for selected Canvas nodes'), which does not clarify that the results are node assets tied to the tool name. It is understandable at a high level but says nothing an agent could not infer from the name alone.

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 guidance on when to use this versus siblings such as ai_modeling_canvas_input_assets, ai_modeling_canvas_asset_get, or ai_modeling_canvas_asset_select. The word 'selected' hints at a precondition but never states it.

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