Skip to main content
Glama

ai_modeling_canvas_projects

Read-only

Lists Canvas projects from your Tripo Studio account with pagination, letting agents browse and select existing projects for further modeling work.

Instructions

List your Canvas projects.

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_projects"
  }
}

Input Schema

NameRequiredDescriptionDefault
offsetNo
pageSizeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

C2.4/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 by structured data. The description adds nothing beyond that: it does not mention pagination behavior, ordering, default page size, or the shape of the result, all of which matter for a list operation.

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?

The single sentence is front-loaded and free of filler, which is good. But its brevity comes from omission rather than economy, leaving the definition under-specified rather than tight.

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 paginated list tool with two undocumented parameters and no output schema, the description should at least explain paging and what a project record contains. Annotations cover the read-only safety profile, but the operational essentials an agent needs to call this correctly are missing.

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 offset and pageSize have no documented meaning in either the schema or the description. The description does not compensate at all — it never references paging, limits, or defaults, so an agent must guess how to page through results.

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 pairs a specific verb ('List') with a specific resource ('Canvas projects'), so the basic operation is unambiguous. However, it does nothing to distinguish this from closely named siblings such as ai_modeling_canvas_get_project, ai_modeling_canvas_batches, or ai_modeling_canvas_events, leaving the agent to infer the boundary from names alone.

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 use this tool, when not to, or which sibling to prefer for a single project versus a batch listing. The agent gets no routing guidance beyond the word 'List'.

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