Skip to main content
Glama

ai_modeling_gallery_collect

Add a gallery model to your collection using its ID so you can organize and revisit saved 3D assets in your Tripo Studio account.

Instructions

Add a gallery model to your collection.

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": {
      "id": "<id>"
    },
    "name": "ai_modeling_gallery_collect"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

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 need not restate that this mutates remote state. It nevertheless adds nothing about what happens when the model is already collected (idempotency or error), whether the change is reversible, or what the call returns.

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, front-loaded sentence with no filler or redundancy. Its brevity is efficient rather than padded, though it leaves the definition under-specified overall.

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 mutation tool with no output schema, one undocumented id parameter, and no annotations covering permissions or duplicate handling, the description is far too thin to call confidently. An agent cannot tell what a valid id looks like or what result to expect.

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 the single required 'id' parameter is undocumented in both schema and description. The phrase 'gallery model' only weakly implies the id identifies a gallery item, and nothing is said about the accepted pattern, length limits, or where such an id is obtained.

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 verb 'Add' plus the resource 'a gallery model' and the destination 'your collection' make the operation concrete. It does not, however, contrast itself with adjacent siblings such as ai_modeling_gallery_like or ai_modeling_gallery_uncollect, leaving the agent to infer the difference.

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 statement of prerequisites (authentication or a selected account), and no pointer to the reverse operation ai_modeling_gallery_uncollect. The agent must guess the context in which collection rather than liking is the intended action.

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