Skip to main content
Glama

ai_modeling_share_templates

Read-only

Lists supported Tripo Studio share-image templates and local video capabilities to help agents choose compatible options for sharing and video tasks.

Instructions

list supported Studio share-image templates and local video capabilities

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

B3.1/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already state readOnlyHint=true, destructiveHint=false and openWorldHint=true, and the description's 'list' wording is consistent with a safe read, so there is no contradiction. Beyond that it adds only the resource scope; it says nothing about whether the call reaches a remote Studio service (which openWorldHint implies) or inspects the local machine for video support, nor about pagination or result shape.

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 repetition. It is terse rather than padded, though the terseness is part of why guidance and return-format detail are absent.

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?

For a zero-parameter discovery call with no output schema, the description should at least hint at the return shape (e.g. template identifiers that feed into ai_modeling_share_image) or explain what 'local video capabilities' means. It names the subject matter but leaves the agent unable to anticipate what it will receive or how to use it downstream.

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

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline is 4. No parameter-level detail is missing because no inputs exist.

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 verb 'list' plus the resources 'Studio share-image templates' and 'local video capabilities' gives the agent a reasonable idea of what comes back, but it is a compound purpose and the description never distinguishes it from neighbors such as ai_modeling_image_templates, ai_modeling_canvas_templates or ai_modeling_share_image. The word 'supported' is not defined, so the scope boundary stays fuzzy.

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 stated prerequisites, and no exclusion against the template-listing siblings. An agent can guess this is a discovery call, but the description supplies nothing that helps it choose between this and the other *_templates tools.

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