Skip to main content
Glama

ai_modeling_canvas_texture_reference

Read-only

Prepare webpage Texture reference inheritance for a saved canvas node, returning guarded edit actions from upstream images or the exact model version; save and run separately.

Instructions

Prepare the webpage Texture reference inheritance for a saved node. Returns guarded canvas-edit actions from upstream images or the exact model version; save and run separately.

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

Input Schema

NameRequiredDescriptionDefault
nodeIdYes
canvasIdYes
revisionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description is consistent with that by framing the output as 'guarded canvas-edit actions' rather than an actual edit. It adds modest context (actions derive from upstream images or the exact model version), but does not say what 'guarded' means, whether results are cached, or what happens with an unsaved node.

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?

Two sentences with no filler, and the verb is front-loaded. However, the first sentence is dense with undefined internal jargon ('webpage Texture reference inheritance'), which costs comprehension in an otherwise short definition.

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, 0% parameter coverage, and open-world behavior declared, the description carries a heavy burden and does not meet it: the shape of the returned 'guarded canvas-edit actions', how revision affects results, and the save/run follow-up are all underspecified for a tool whose output must be applied elsewhere.

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 all three parameters (canvasId, nodeId, revision) rely on the description for meaning. It conveys only that the node is 'saved' (hinting nodeId) and vaguely gestures at 'the exact model version' (possibly revision), leaving the revision selector and id formats undocumented.

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 names a resource ('Texture reference inheritance for a saved node') and an outcome ('Returns guarded canvas-edit actions'), so an agent can infer this is a prepare/plan step rather than a mutator. But the phrasing is jargon-heavy and vague – 'Prepare the webpage Texture reference inheritance' does not clearly tell what the tool produces, and no sibling is named to differentiate it from tools like ai_modeling_canvas_graph_edit or ai_modeling_canvas_input_assets.

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?

'save and run separately' communicates an implied workflow: this tool yields actions you must apply elsewhere, not a direct mutation. That is useful implied usage, but there is no explicit when-to-use condition, no exclusion of alternatives, and no stated prerequisites (e.g., whether the node must already exist or be saved first).

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