Skip to main content
Glama

ai_modeling_gallery_browse

Read-only

Search and filter gallery 3D models by category, topology, material, use case, and sort order to find models for projects or 3D printing.

Instructions

Search and filter gallery models by category, topology, material, use case and sort order.

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

Input Schema

NameRequiredDescriptionDefault
sortNorecommended
queryNo
categoryNofeatured
use_caseNoall
page_sizeNo
model_typeNoall
page_tokenNo
featured_onlyNo

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, openWorldHint and destructiveHint=false, so safety is covered. The description adds nothing beyond that: it doesn't mention pagination via page_token, whether results are stable, or how sorting interacts with filtering, despite these being central to a paging browse tool.

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 redundancy. It is efficient, though its brevity is partly the cause of the missing detail rather than a sign of discipline.

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?

With eight parameters, zero schema descriptions, no output schema, and no annotations about results, the definition leaves an agent guessing about pagination, filtering combinations and the query text field. It does not supply enough for confident invocation.

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% across 8 parameters, so the description must compensate. It only gestures at category, use_case and sort, mentions a nonexistent "material" field, and never explains query, model_type, featured_only, page_size or page_token — leaving most parameters with only their enum values for meaning.

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 pair ("search and filter") and resource ("gallery models"), which is clear on its own. However it names facets like "topology" and "material" that do not correspond to any actual parameter, and it does not distinguish itself from the sibling ai_modeling_gallery_search.

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?

No guidance on when to use this browser versus the similarly named ai_modeling_gallery_search, or when to prefer it over feed/item tools. The only implied usage is 'browse the gallery', which the sibling names already suggest.

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