Skip to main content
Glama

ai_modeling_canvas_asset_select

Select a generated canvas asset by node and asset ID so downstream nodes can use that result in your modeling workflow.

Instructions

Select one generated result for downstream 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": {
      "nodeId": "<nodeId>",
      "assetId": "<assetId>"
    },
    "name": "ai_modeling_canvas_asset_select"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeIdYes
assetIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

C2.2/5.0
Behavior2/5

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

Annotations already declare a non-read-only, non-destructive, open-world mutation, and "Select" is consistent with that, so there is no contradiction. Beyond that the description discloses nothing: it does not say that selecting mutates canvas/graph state, whether a prior selection is replaced, whether the operation is reversible, or what confirmation is returned.

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 front-loaded sentence with no filler, so nothing needs trimming. The problem is under-specification rather than verbosity — brevity here costs information rather than aiding scanning.

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 two-required-parameter mutation with no output schema and zero parameter documentation, the description should carry most of the burden and does not. An agent knows roughly what the tool does but not the identity/validity of ids, side effects, or the relationship to batch_select.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and both parameters (nodeId, assetId) are required, yet the description never references either one. An agent must open the schema and still guess that nodeId identifies the owning node and assetId the chosen result; the description contributes no meaning.

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?

"Select one generated result" gives a concrete verb and object, and the word "one" implicitly distinguishes this from ai_modeling_canvas_batch_select. However, "generated result" is never defined (image? node output?), and the description does not say what is being selected from or what the selection affects.

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?

"for downstream nodes" hints at the workflow position (pick an output so later nodes can consume it), which is the only usage signal present. There is no explicit when-to-use, no prerequisite (e.g., generation must have completed), and no statement about when to prefer batch_select instead.

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