Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

list_design_templates_catalog

Read-only

Browse all design templates Kiln can render: parametric parts that compile locally and design-pattern guidance. Check each entry's generatable flag to know the next call.

Instructions

Browse the whole design-template library, both kinds.

        Returns every PARAMETRIC PART Kiln can render on its own —
        brackets, bins, stands, cases, hooks, jigs, clamps, plumbing
        and garden parts — followed by the DESIGN PATTERNS that are
        guidance rather than geometry.  Every entry carries a
        ``generatable`` flag and the call to make next.

        The parametric parts are FREE and need no AI provider: they
        compile locally through OpenSCAD.  Reach for one whenever a
        user wants a functional part to their own dimensions, and
        offer it before writing OpenSCAD from scratch — it is
        faster and every part in the library is print-verified.

        Use ``find_design_templates(use_case)`` to search rather than
        reading the whole catalog.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only declare the read-only/non-destructive profile; the description adds real behavioral context the agent could not otherwise know: entries carry a generatable flag and a next-call hint, parametric parts compile locally via OpenSCAD, are free, require no AI provider, and are print-verified. It stops short of describing result size or pagination for a whole-library listing.

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 scope, then the return shape, then the routing advice; each sentence carries information. Slightly longer than necessary with emphatic capitalization and a somewhat redundant restatement of the two entry kinds.

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 does the work of explaining what comes back (both entry kinds, generatable flag, next call) and why the parts matter (free, local, print-verified). Missing only scale/pagination expectations for a full-catalog browse, which matters for a zero-arg list tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes no parameters, so baseline is 4. The description usefully redirects parameterized searching to find_design_templates(use_case), clarifying the intended argument shape of the alternative rather than this tool's empty schema.

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 ('Browse the whole design-template library') and scopes it as returning two entry kinds: parametric parts and design patterns. It does not name the most likely confusing sibling, list_design_templates, so sibling differentiation is only partial.

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

Usage Guidelines5/5

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

Gives explicit when-to-use ('a user wants a functional part to their own dimensions'), a preference rule ('offer it before writing OpenSCAD from scratch'), and a when-not-to rule routing to find_design_templates(use_case) instead of reading the whole catalog.

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