Skip to main content
Glama

ai_modeling_library_list

Read-only

Lists your 3D models or active team workspace models, filtered by operation type, with pagination for browsing and managing Studio assets.

Instructions

List your models or models in the active team workspace, filtered by operation type.

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

Input Schema

NameRequiredDescriptionDefault
typeNoall
scopeNomine
page_sizeNo
page_tokenNo

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?

Annotations already declare this a non-destructive, read-only, open-world operation, so the safety profile is covered. The description adds the scope semantics (personal vs team workspace), which is useful, but says nothing about result volume, ordering, or pagination behavior, which matters for a list tool whose default page size is 20.

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 front-loaded sentence with no filler, which is appropriate for a simple list operation. It is efficient, though the phrase 'operation type' is imprecise rather than economical.

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 4-parameter, paginated tool with no output schema and zero schema description coverage, the description leaves too much unexplained — the meaning of the type enum, the scope default, and how to page through results are all invisible to an agent.

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 description carries the full burden and largely fails. 'Filtered by operation type' is ambiguous against a parameter actually named 'type' with values rigged/smart_mesh/textured/untextured — nothing explains what an 'operation type' is or that 'all' is the default; page_size, page_token, and their limits are entirely unaddressed.

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?

States a specific verb and resource ('List your models') and distinguishes the two scopes it can return: personal models versus models in the active team workspace. It stops short of differentiating itself from plausible neighbors such as ai_modeling_library_user_items, so it is clear but not sibling-aware.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The dual-scope framing implies when to reach for this tool (you want a listing across your own or the team workspace), but there is no explicit when-not guidance, no prerequisites, and no named alternative for related listing needs.

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