Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

search_design_templates

Read-only

Find 3D design templates by natural-language query with fuzzy matching across IDs, categories, and tags, returning relevance-ranked results you can filter by category.

Instructions

Search the template library by natural-language description.

Fuzzy keyword matching against template IDs, descriptions, categories,
and tags.  Returns scored matches ranked by relevance.

:param query: Natural-language search string (e.g. "phone stand", "hook").
:param max_results: Maximum number of results (default 10).
:param category_filter: Optional category to limit results (e.g. "hardware").
:returns: Dict with matches list, each containing template_id, score,
          description, and category.

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_design_templates"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesNatural-language search string (e.g. "phone stand", "hook").
max_resultsNoMaximum number of results (default 10). Default: 10.
category_filterNoOptional category to limit results (e.g. "hardware"). Default: "".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.5.1
    • changedInput schema / properties / category_filter / description
      Previous value: -"Default: \"\"."New value: +"Optional category to limit results (e.g. \"hardware\"). Default: \"\"."
    • changedInput schema / properties / max_results / description
      Previous value: -"Default: 10."New value: +"Maximum number of results (default 10). Default: 10."
    • addedInput schema / properties / query / description
      Added value: +"Natural-language search string (e.g. \"phone stand\", \"hook\")."
  2. Changed4 schema fields changedv1.5.0
    • removedInput schema / properties / category_filter / default
      Removed value: -""
    • addedInput schema / properties / category_filter / description
      Added value: +"Default: \"\"."
    • removedInput schema / properties / max_results / default
      Removed value: -10
    • addedInput schema / properties / max_results / description
      Added value: +"Default: 10."
  3. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the read-only/safe profile needs no restating. The description adds genuine value beyond them by disclosing the matching algorithm (fuzzy keyword against IDs, descriptions, categories, tags) and the relevance ranking, though it says nothing about result caps, empty-result behavior, or scoring range.

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?

Front-loaded with the core action and mechanism in the first two sentences; every line contributes something. The Sphinx-style :param block is somewhat redundant against the already-complete schema, which keeps it from a 5.

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 :returns line usefully documents the response shape (matches list with template_id, score, description, category), which is exactly the missing piece. Combined with the annotation-covered safety profile, the definition is nearly complete, missing only sibling routing and edge-case behavior.

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 the description's :param lines repeat the schema text verbatim (query, max_results, category_filter), adding no new meaning. The schema already carries the defaults and examples, so baseline 3 applies.

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+resource ("Search the template library") and adds the matching mechanism (fuzzy keyword matching over IDs, descriptions, categories, tags) and the ordering (scored, relevance-ranked). It does not, however, distinguish itself from near-identical siblings such as find_design_templates, list_design_templates, or match_design_requirements, so the agent gets a clear purpose but no disambiguation.

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 by the phrase "natural-language description" and the optional category filter; there is no explicit when-to-use, when-not-to-use, or named alternative. Given the dense cluster of template-related siblings, this is a real gap, but the tool's role is inferable from the description.

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