Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

list_proven_recipes

Read-only

Retrieve proven recipes across all designs or filter by design to reuse validated 3D printing settings and avoid failed prints.

Instructions

List all proven recipes across all designs (Pro).

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of recipes to return (default 50). Default: 50.
design_idNoOnly this design's recipes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.5.1
    • addedInput schema / properties / design_id / description
      Added value: +"Only this design's recipes."
    • changedInput schema / properties / limit / description
      Previous value: -"Default: 50."New value: +"Maximum number of recipes to return (default 50). Default: 50."
  2. Addedv1.5.0

TDQS

B3.3/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. The description adds one piece of context beyond that — the '(Pro)' tier gate, implying access may require a paid tier — but says nothing about ordering, pagination, or what an empty result means.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence with the resource and scope front-loaded and no filler. Nothing superfluous is present.

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

Completeness3/5

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

For a trivial two-optional-parameter read tool with a complete schema and read-only annotations, this is close to sufficient. The remaining gap is the tension between 'across all designs' and the design_id filter, plus no hint about result ordering or whether evidence/lineage of recipes is included.

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%, so both limit and design_id are documented in the schema. The description adds no syntax or format detail, and 'across all designs' actually cuts against the existence of the design_id filter, slightly muddying rather than clarifying parameter meaning.

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 ('List all proven recipes') plus a scope ('across all designs'), which is enough to separate it from most siblings. However, it never names the closely-related get_proven_recipe and record_proven_recipe, so the list-vs-single-vs-write distinction must be inferred from the names alone.

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?

The description gives no when-to-use guidance and no alternatives. An agent browsing recipes cannot tell from the text whether to call this to enumerate recipes or get_proven_recipe to fetch a specific one, and nothing indicates when the design_id filter should be preferred over a full listing.

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