Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

search_design_versions

Read-only

Find the right design version by querying prompts, notes, or names; get matching records newest first plus the search scope.

Instructions

Search design versions by prompt, notes, or design name.

        Scans all design directories under ``~/.kiln/designs/`` for
        versioned recipe files whose prompt, notes, or name fields
        contain the query string (case-insensitive).

        Args:
            query: The search term (literal substring, not regex).
            limit: Maximum number of results to return (default 10).

        Returns:
            A list of matching version records, newest first, plus a
            ``scope`` block saying which store was searched and
            whether the user's cloud-side versions were included.  A
            miss here is only a miss in the stores ``scope`` names.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results to return (default 10). Default: 10.
queryYesThe search term (literal substring, not regex).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.5.1
    • changedInput schema / properties / limit / description
      Previous value: -"Default: 10."New value: +"Maximum number of results to return (default 10). Default: 10."
    • addedInput schema / properties / query / description
      Added value: +"The search term (literal substring, not regex)."
  2. Changed2 schema fields changedv1.5.0
    • removedInput schema / properties / limit / default
      Removed value: -10
    • addedInput schema / properties / limit / description
      Added value: +"Default: 10."
  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 readOnly/closed-world/no-destruction, and the description goes beyond them by disclosing case-insensitive substring matching, newest-first ordering, and the partial-coverage caveat about cloud-side versions. The only real omission is result-count or pagination behavior on a limit hit.

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 prose paragraph is well front-loaded, but the Args section duplicates the schema field descriptions word for word, wasting space. The Returns paragraph earns its place since there is no output schema.

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 sketches the return shape (matching version records newest first plus a scope block), which is exactly the missing piece. Remaining gaps are minor, such as what a version record contains or how limit truncation is signalled.

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 Args block restates both parameters nearly verbatim from the schema. The description adds no format guidance, matching rules, or interaction between query and limit beyond what the schema already states, 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?

The first sentence gives a specific verb and resource plus the three searchable fields (prompt, notes, name), which is enough to separate it from list_design_versions or get_design_version. It never names those siblings explicitly, so the differentiation is implicit rather than stated.

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?

It scopes the search to the local design store under ~/.kiln/designs/ and warns that a miss is only a miss within the stores the scope block names, which is useful context. It never says when to prefer this over list_design_versions, list_designs, or cross-store search, so the agent must infer the boundary.

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