Skip to main content
Glama

Find printable models

find_models
Read-onlyIdempotent

Search Printables for ready-made 3D models. Returns titles, designers and page links; the customer downloads their pick and drops it into ply's card.

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": "find_models"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesWhat to look for, e.g. 'milwaukee m18 battery holder'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only, open-world and idempotency, so the bar is lower; the description still adds real value by disclosing the return shape (titles, designers, page links) and that it does NOT fetch the model — the customer downloads it and drops it into ply's card. That downstream handoff is exactly the kind of behavioral context annotations can't express. Missing only result-count/pagination or rate-limit notes for an open-world external search.

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 sentences, zero filler: what it searches, what comes back, and what the agent/customer does next. Return shape is front-loaded before the workflow note.

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?

For a one-parameter read-only search with a rich annotation set and no output schema, the description covers purpose, returns, and the handoff workflow. The only gap is any sense of result volume or pagination behavior, which matters somewhat for an open-world external search.

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 coverage is 100% and the single 'query' parameter already carries an example, so the schema does the heavy lifting. The description implies the parameter is a free-text search phrase but adds no syntax, wildcard, or length guidance beyond what the schema provides — baseline 3.

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 ('Search Printables for ready-made 3D models') and names the external source, which distinguishes it from the local-fabrication siblings like make_part and recommend_material. It doesn't explicitly contrast itself with price_model_link or order_part, but the 'ready-made, downloadable' framing makes the boundary readable.

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 word 'ready-made' implicitly signals when to use this versus make_part (custom fabrication), but the description never states that alternative or any exclusions/preconditions. Usage is inferable rather than instructed.

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