Skip to main content
Glama

ai_modeling_gallery_search

Read-only

Search the Studio model gallery by keyword to find 3D models and assets matching your prompt, with optional locale filtering for localized results.

Instructions

Search the Studio model gallery.

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": {
      "user_input": "<user_input>"
    },
    "name": "ai_modeling_gallery_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNoen
user_inputYes

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, destructiveHint=false, and openWorldHint=true, so the safety profile is covered structurally. The description adds nothing beyond that — no indication of what is searched (titles, tags, prompts), how results are ranked, whether results are paginated, or what calling the open-world gallery implies.

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 front-loaded and free of filler, so there is nothing to trim. The problem is the opposite of verbosity: it is too underspecified for a tool with two undocumented parameters and multiple close siblings.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (2 parameters, no nested objects, no output schema) and that annotations cover the read-only open-world profile, the description's main remaining obligation is to explain the query parameter and how this differs from browse. It does neither, leaving the agent to infer query semantics and tool selection.

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 of explaining the two parameters, yet it says nothing about user_input (the required query string, 1-300 chars) or locale (default "en", pattern-constrained). The word "Search" only weakly implies that a query term is expected.

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 description names a specific verb ("Search") and resource ("Studio model gallery"), so an agent can tell it is a query operation over gallery models. However, it offers no differentiation from clearly related siblings such as ai_modeling_gallery_browse, ai_modeling_gallery_feed, or ai_modeling_gallery_tag, leaving the boundary ambiguous.

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 guidance about when to use this tool versus browsing, the feed, or tag-based retrieval. No prerequisites, no exclusions, and no stated conditions under which search is the right choice are provided.

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