Skip to main content
Glama

ai_modeling_canvas_save_to_studio

Save Canvas results into the Studio asset library by passing asset IDs, so agents can persist generated images and 3D assets directly to the user's Studio account for later use.

Instructions

Save Canvas results into the Studio asset library.

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": {
      "assetIds": "<assetIds>"
    },
    "name": "ai_modeling_canvas_save_to_studio"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetIdsYes

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=false, destructiveHint=false and openWorldHint=true, so the description carries no obligation to re-state safety. It adds nothing beyond them: no mention of whether existing Studio assets are overwritten, what happens on partial failure, or whether authentication/ownership of the target library is required.

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 no filler or redundancy. Brevity is commendable, though it tips into under-specification rather than tightness.

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?

This is a mutating, open-world write into an external library with no output schema and an undocumented parameter; the description should at minimum identify the parameter's meaning and the effect of a re-save. None of that is present, so an agent cannot call it confidently without inspecting the schema.

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 'assetIds', and the description never mentions it. It does not explain what kind of IDs these are (Canvas result asset IDs?), the 1–100 item limit, or where the agent obtains them, so the schema constraint carries the full, unexplained burden.

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 ('Save') and both the source and destination ('Canvas results' into the 'Studio asset library'), so the operation is unambiguous on its own. It does not distinguish itself from the sibling 'ai_modeling_canvas_save', leaving the agent unable to tell how the two save paths differ.

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 statement of when to choose this over 'ai_modeling_canvas_save' or any other save-related sibling, and no preconditions (e.g. whether the canvas must already be persisted). The agent is left to infer the selection criterion entirely.

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