Skip to main content
Glama

ai_modeling_canvas_create

Create an empty Canvas project to start organizing and building AI modeling assets in Tripo Studio.

Instructions

Create an empty Canvas project.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ai_modeling_canvas_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo

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 this is a non-read-only, non-destructive, open-world operation, so mutation status is covered. The description adds only the fact that the resulting canvas is empty; it says nothing about whether the caller/workspace context is required, whether the call is idempotent, or what happens on duplicate names.

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 short sentence with no filler, and the verb and scope are front-loaded. It is lean to the point of under-specification, but there is no wasted wording or burying of key information.

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 creation tool in a large sibling family, the description omits what the agent needs next: no mention that a project identifier is returned for use with ai_modeling_canvas_get_project or graph_edit, and no explanation of the optional name parameter. Annotations cover safety but not these workflow essentials.

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?

There is one parameter (name) with 0% schema description coverage, so the description carries the full burden and mentions nothing about it. It doesn't say the parameter is optional, what naming constraints or uniqueness apply, or what name is used when it is omitted (0 required parameters).

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?

Specific verb plus resource: 'Create' an 'empty Canvas project'. The word 'empty' implicitly distinguishes it from the template-based creators among the siblings (from_template, template_create), so an agent can tell it makes a blank canvas rather than a pre-populated one.

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?

No when-to-use guidance at all: nothing says when to pick this over ai_modeling_canvas_from_template or ai_modeling_canvas_template_create, and no prerequisites or follow-up steps are given. The only hint is the adjective 'empty'.

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