Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

search_cached_models

Read-only

Search locally cached 3D models by name, prompt, source, or tags to find files already available on this machine before downloading or regenerating them.

Instructions

Search the local model cache by name, source, tags, or prompt text.

        Args:
            query: Free-text search against file name, prompt, and tags.
            source: Filter by source (e.g. ``"thingiverse"``).
            tags: Comma-separated tags to filter by.
            limit: Maximum results (default 20).

        The response declares its ``scope``: this cache is local to
        this machine, so the count is what THIS install has cached,
        not everything the user has ever downloaded or generated.

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

Input Schema

NameRequiredDescriptionDefault
tagsNoComma-separated tags to filter by.
limitNoMaximum results (default 20). Default: 20.
queryNoFree-text search against file name, prompt, and tags.
sourceNoFilter by source (e.g. ``"thingiverse"``).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.5.1
    • changedInput schema / properties / limit / description
      Previous value: -"Default: 20."New value: +"Maximum results (default 20). Default: 20."
    • addedInput schema / properties / query / description
      Added value: +"Free-text search against file name, prompt, and tags."
    • addedInput schema / properties / source / description
      Added value: +"Filter by source (e.g. ``\"thingiverse\"``)."
    • addedInput schema / properties / tags / description
      Added value: +"Comma-separated tags to filter by."
  2. Changed5 schema fields changedv1.5.0
    • removedInput schema / properties / limit / default
      Removed value: -20
    • addedInput schema / properties / limit / description
      Added value: +"Default: 20."
    • removedInput schema / properties / query / default
      Removed value: -null
    • removedInput schema / properties / source / default
      Removed value: -null
    • removedInput schema / properties / tags / default
      Removed value: -null
  3. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint=false, so safety is covered. The description adds genuinely useful context beyond that: results are scoped to this machine's cache, so counts are install-local rather than global history. It still doesn't say what happens with zero matches or how results are ordered.

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 opening sentence and the scope caveat both earn their place and are front-loaded. The middle Args block is redundant with the input schema and pads the definition without adding information, which dilutes conciseness.

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?

With no output schema, the description usefully explains that the response declares a 'scope' field and what that scope means. Combined with the parameter documentation, an agent has enough to call the tool correctly; only result-ordering and empty-result behavior are left unaddressed.

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%, so the schema already documents all four parameters. The Args block in the description largely restates those same texts verbatim (query against file name/prompt/tags, source example, comma-separated tags, default limit 20), adding no new semantics such as matching behavior, case sensitivity, or multi-tag AND/OR logic.

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 the local model cache') and names the searchable facets (name, source, tags, prompt text). It does not explicitly differentiate itself from near-siblings like list_cached_models, get_cached_model, or search_all_models, so an agent must infer the distinction from the word 'search' versus 'list'.

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?

Usage is only implied: searching is what you do when you want to locate a cached model by text. There is no statement of when to prefer this over list_cached_models or search_all_models, and no note about behavior when no parameters are supplied (all are optional).

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