Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

search_models

Read-only

Search Thingiverse for 3D-printable models by keyword, with sorting and pagination. Returns model summaries with creator, thumbnail, and download and like counts.

Instructions

Search Thingiverse for 3D-printable models.

        Args:
            query: Search keywords (e.g. "raspberry pi case", "benchy").
            page: Page number for pagination (1-based, default 1).
            per_page: Results per page (default 10, max 100).
            sort: Sort order — "relevant", "popular", "newest", or "makes".

        Returns a list of model summaries including name, creator, thumbnail,
        and download/like counts.  Use ``model_details`` with the ``id`` to
        get full information, and ``model_files`` to see downloadable files.

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
pageNoPage number for pagination (1-based, default 1). Default: 1.
sortNoSort order — "relevant", "popular", "newest", or "makes". Default: "relevant".
queryYesSearch keywords (e.g. "raspberry pi case", "benchy").
per_pageNoResults per page (default 10, max 100). Default: 10.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.5.1
    • changedInput schema / properties / page / description
      Previous value: -"Default: 1."New value: +"Page number for pagination (1-based, default 1). Default: 1."
    • changedInput schema / properties / per_page / description
      Previous value: -"Default: 10."New value: +"Results per page (default 10, max 100). Default: 10."
    • addedInput schema / properties / query / description
      Added value: +"Search keywords (e.g. \"raspberry pi case\", \"benchy\")."
    • changedInput schema / properties / sort / description
      Previous value: -"Default: \"relevant\"."New value: +"Sort order — \"relevant\", \"popular\", \"newest\", or \"makes\". Default: \"relevant\"."
  2. Changed6 schema fields changedv1.5.0
    • removedInput schema / properties / page / default
      Removed value: -1
    • addedInput schema / properties / page / description
      Added value: +"Default: 1."
    • removedInput schema / properties / per_page / default
      Removed value: -10
    • addedInput schema / properties / per_page / description
      Added value: +"Default: 10."
    • removedInput schema / properties / sort / default
      Removed value: -"relevant"
    • addedInput schema / properties / sort / description
      Added value: +"Default: \"relevant\"."
  3. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so safety and external-source behavior are covered. The description adds useful behavioral context beyond annotations by describing the return content: model summaries with name, creator, thumbnail, and download/like counts. It does not mention rate limits or API error behavior, but the core result shape is disclosed.

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?

The description is front-loaded with its purpose and then uses a readable Args/Returns structure. It is not bloated, but the Args section largely duplicates parameter descriptions that are already fully documented in the schema, so it is not maximally concise.

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?

Because there is no output schema, the description usefully explains that results are model summaries with creator, thumbnail, and download/like counts. It also points to model_details and model_files for follow-up actions. The main remaining gap is that it does not clarify when to use this Thingiverse search versus the other available model-search tools.

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%, and every parameter in the description also has a matching schema description with defaults and sort values. The description therefore does not add new meaning beyond the schema; it mostly repeats the same parameter documentation. The baseline of 3 is appropriate when the schema already does the heavy lifting.

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 gives a specific verb and resource: 'Search Thingiverse for 3D-printable models.' It clearly scopes the tool to Thingiverse and distinguishes downstream steps by naming model_details and model_files. It does not distinguish itself from other search siblings such as search_all_models or browse_models, so it stops short of full sibling differentiation.

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 description explains what to do after a search by directing the agent to model_details for full information and model_files for downloadable files. However, it does not state when to use this tool instead of search_all_models, browse_models, or search_cached_models, leaving the main routing decision implicit.

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