Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

best_design_version

Read-only

Ranks supplied design versions by success rate and returns the leading version, optionally filtered by material or printer.

Instructions

Find the version with the highest success rate.

Needs Kiln Pro.

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": {
      "version_ids": "<version_ids>"
    },
    "name": "best_design_version"
  }
}

Input Schema

NameRequiredDescriptionDefault
materialNoOptional material filter (e.g. "PETG"). Default: "".
printer_idNoOptional printer filter. Default: "".
version_idsYesList of version IDs to evaluate.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.5.1
    • changedInput schema / properties / material / description
      Previous value: -"Default: \"\"."New value: +"Optional material filter (e.g. \"PETG\"). Default: \"\"."
    • changedInput schema / properties / printer_id / description
      Previous value: -"Default: \"\"."New value: +"Optional printer filter. Default: \"\"."
    • addedInput schema / properties / version_ids / description
      Added value: +"List of version IDs to evaluate."
  2. Addedv1.5.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, and openWorldHint=false, so the safety profile is covered. The description adds the Kiln Pro entitlement requirement, which is genuine behavioral context not in the annotations, but it omits tie-breaking behavior, data source for 'success rate', and what the response contains.

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?

Two short lines with zero waste: the purpose is front-loaded, and the prerequisite is separated so it cannot be missed. Nothing is repeated from the schema or annotations.

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?

There is no output schema, so the description should say something about what comes back (a version ID, a scored comparison, a ranked list) and how ties or zero-success candidates are handled. The Pro gate is covered, but the return contract is left entirely implicit for a tool whose output an agent must act on.

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 all three parameters (version_ids, material, printer_id) carry their own descriptions including defaults and examples. The description adds no parameter meaning beyond the schema, 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 plus a ranking criterion: 'Find the version with the highest success rate.' An agent can distinguish this from list_design_versions, get_design_version, compare_design_versions, and design_version_health, though the description does not name any of those siblings explicitly.

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?

'Needs Kiln Pro' gives a real usage gate (paid tier required), which helps an agent decide whether to call it at all. However, there is no guidance on when to prefer this over the many sibling version-inspection tools, or what to do when no version has a success rate.

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