Skip to main content
Glama

ai_modeling_canvas_lab_instructions

Read-only

Retrieve saved creative instructions attached to a Lab node by node ID, enabling agents to reuse prior Canvas guidance during image and 3D modeling workflows.

Instructions

Read the saved creative instructions attached to a Lab 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_lab_instructions"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

C2.9/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 safety is covered. The description adds only the word 'saved', implying persisted state, and says nothing about behavior for a missing or invalid node, what happens with a node that has no instructions, or the shape of what is returned. Beyond annotations, the added behavioral context is minimal.

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?

One short sentence with the resource and scope front-loaded and no filler. It is efficient, though its brevity is partly the source of the gaps noted elsewhere rather than pure economy.

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?

This is a simple single-parameter read tool with annotations covering the safety profile and no output schema, so the description need not explain return values. Still, an agent does not learn what 'creative instructions' actually contain (free text, structured prompt, etc.) or what happens when none exist, which matters for deciding how to use the result.

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

Parameters3/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 nodeId parameter, so the description must carry the burden. It does add real meaning by indicating the ID refers to a Lab node whose attached instructions are read, rather than a canvas or project ID. However, it gives no format, source, or resolution guidance for the identifier.

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 names a specific verb and resource: read the saved creative instructions attached to a Lab node. That is concrete and distinguishable from the broader canvas lab family. It does not explicitly differentiate itself from near-neighbors such as ai_modeling_canvas_lab_inputs or ai_modeling_canvas_lab_plan, so it stops short of a 5.

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 preconditions, and no mention of alternatives. An agent must infer from the name alone when to call this versus other lab-related readers. The 'attached to a Lab node' phrasing implies context but does not state usage rules.

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