Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

list_design_components

Read-only

Lists pre-built OpenSCAD components from bundled BOSL2 libraries, including gears, threads, screws, bearings, and hinges, with an optional category filter for mechanical, fasteners, or electronics parts.

Instructions

List available pre-built OpenSCAD components from bundled libraries.

        Kiln bundles BOSL2 OpenSCAD libraries with pre-built
        components for gears, threads, screws, bearings, hinges, and more.
        These components produce proven geometry — much better than
        generating complex mechanical parts from scratch.

        Categories: mechanical, fasteners, electronics

        Args:
            category: Optional filter by category. If not provided, lists
                all available components.

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

Input Schema

NameRequiredDescriptionDefault
categoryNoOptional filter by category. If not provided, lists all available components.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.1
    • addedInput schema / properties / category / description
      Added value: +"Optional filter by category. If not provided, lists all available components."
  2. Changed1 schema field changedv1.5.0
    • removedInput schema / properties / category / default
      Removed value: -null
  3. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already make clear that this is a non-destructive, read-only, non-open-world listing operation. The description adds useful domain context about BOSL2 libraries and component types, but it does not disclose return format, pagination, or other behavior beyond the annotations.

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?

The description is front-loaded with the core purpose and remains reasonably efficient. Some phrasing is persuasive padding, and the Args section duplicates the schema, but the overall structure is clear and not excessive.

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?

For a simple listing tool with one optional parameter, full schema coverage, and clear read-only annotations, the description is largely complete. It could say more about the returned items or how the listed components are intended to be used next, but no output schema exists to carry that detail.

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?

Schema coverage is 100% and the schema already explains the optional category filter and its default behavior. The description adds meaning beyond the schema by enumerating the available categories: mechanical, fasteners, and electronics.

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 description clearly states the verb and resource: it lists available pre-built OpenSCAD components from bundled libraries. It distinguishes the resource from generating complex parts from scratch, but it does not explicitly differentiate from related siblings such as match_design_components or list_design_templates_catalog.

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?

The description implies when this tool is useful by saying these components are better than generating complex mechanical parts from scratch. However, it does not explicitly state when to use this tool versus alternatives, nor does it name any sibling tool for a different component-discovery task.

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