Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

search_public_designs

Read-only

Search public designs and their creators on Kiln by keyword, material, license, printer, print count, or file availability; filter and sort results to find printable models.

Instructions

Search the designs people have made public on Kiln, and the people who made them.

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

Input Schema

NameRequiredDescriptionDefault
pageNoWhich page of results, from 1 (the default) up to 100. Default: 1.
sortNo``relevance``, ``newest``, ``most_printed`` or ``most_starred``. Empty, ``relevance`` with words and ``newest`` without; any other word is ``INVALID_QUERY``. Default: "".
queryNoThe search words: a design's name or description, a username or display name, a material. Empty lists every public design, newest first. Default: "".
licenseNoOnly designs under this license: ``cc-by-4.0``, ``cc-by-nc-4.0``, ``cc0-1.0`` or ``all-rights-reserved``. Empty, any license; any other word is ``INVALID_QUERY``. Default: "".
has_fileNo``True`` for only designs whose file can be downloaded. ``False`` (the default) asks nothing. Default: false.
materialNoOnly designs printed in this material type, such as ``PLA``. Empty, any material. Default: "".
printer_modelNoOnly designs printed on this printer model. Empty, any printer. Default: "".
printed_by_minNoOnly designs printed by at least this many people. ``0`` (the default) asks nothing. Default: 0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.1

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered without the description. The description adds a genuine scope fact beyond the annotations — that creators are also searchable entities — which explains why a username query returns results. It says nothing about result ordering, pagination limits, or the error behavior that the schema mentions (INVALID_QUERY).

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?

A single front-loaded sentence with no filler and the verb up front. It is efficient, though its brevity is part of the reason the tool's filtering and pagination capabilities go unmentioned.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is an eight-parameter faceted search tool with sorting, license, material, printer-model, and print-count filters, plus a 100-page pagination cap, yet the description mentions none of that. With no output schema, the description should at least characterize what comes back (designs and creators) and how results are ordered, which it does only vaguely.

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 all eight parameters (page, sort, query, license, has_file, material, printer_model, printed_by_min) are already fully documented in the schema with defaults and accepted values. The description adds only an indirect hint that `query` matches usernames/display names via "the people who made them," so the 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 and resource ("Search the designs people have made public on Kiln") and adds a useful scope note that the search also spans the people who made them. It does not distinguish itself from close siblings such as list_public_designs, get_public_design, or search_models, so an agent cannot tell from the description alone which public-search entry point to pick.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no exclusions, and no named alternative. Nothing says whether to use this versus list_public_designs (browse) or get_public_design (fetch one), nor what an empty query does, even though the schema does address that case.

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