Skip to main content
Glama

models

Search 3D models

search_models
Read-only

Full-text search over the Free3D.io catalog (name, description, tags). Returns model ids — follow up with get_model_card for metadata or download_model (paid).

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": {
      "query": "<query>"
    },
    "name": "search_models"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results, 1-25 (default 10)
queryYesSearch text, e.g. "ikea chair"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, so the description carries the rest. It adds real behavioral context: the search is full-text across name/description/tags, it returns ids rather than full records, and downloading is paid. It stops short of describing result ordering or pagination behavior, but the key traits are disclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with what the tool does and followed by what to do next. Every clause carries information; no filler or redundancy.

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?

No output schema exists, but the description compensates by stating that it returns model ids, which is the critical fact for chaining to get_model_card. Slight gap in not mentioning result ordering or empty-result behavior, but for a two-parameter read-only search this is nearly complete.

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

Parameters3/5

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

Schema description coverage is 100% — both query and limit are documented, including the 1-25 range and default of 10. The description adds nothing about parameters beyond what the schema already says, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('full-text search') and resource ('Free3D.io catalog'), and narrows scope by naming the searched fields (name, description, tags) and the return type (model ids). This distinguishes it clearly from get_model_card and download_model, which are the follow-up steps rather than search variants.

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

Usage Guidelines4/5

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

Explicitly tells the agent when to use this versus the siblings: call this to find ids, then use get_model_card for metadata or download_model for paid acquisition. No exclusion guidance is offered (e.g. no limits on query syntax or what happens with zero results), but the routing to alternatives is clear and actionable.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources