Skip to main content
Glama

ai_modeling_collection_list

Read-only

List or search models in a Studio collection using query filters and paginated results to browse and select available 3D assets.

Instructions

List or search the models in your Studio collection.

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

Input Schema

NameRequiredDescriptionDefault
queryNo
page_sizeNo
page_tokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered by structured data. The description adds nothing further: it does not disclose pagination behavior, how page_token interacts with query, result caps, or whether searching is server-side, all of which matter for a paged search endpoint.

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 efficient and front-loaded with the action, with no filler or redundancy. Its brevity is, however, the result of under-specification rather than disciplined editing, so it does not earn a high score.

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, optionally filtered list tool with three undocumented parameters and no output schema, the description should explain the query/page_size/page_token contract and the shape of results. As written, an agent would have to guess how to page and how results are ordered.

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 must carry parameter meaning, yet it only loosely hints at a query filter via the word 'search'. The page_size and page_token parameters and their roles in pagination are completely undocumented in both schema and description, leaving two of three parameters ambiguous.

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/search models in the user's Studio collection. It is clear what the tool returns at a high level, but it does not distinguish itself from similar siblings such as ai_modeling_library_list or ai_modeling_assets_list, so an agent cannot tell from the text alone which collection tool applies.

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?

'List or search' implies the two usage modes (unfiltered enumeration vs. query), which is implied guidance for picking a call style. However, there is no statement of when to prefer this over the library/assets/motion list siblings, no mention of prerequisites, and no guidance on paging through results.

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