Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

auto_add_rubber_feet

Adds rubber foot positions to the bottom of an STL model, then opens an interactive 3D stage to inspect the result.

Instructions

Add rubber foot positions to model bottom (Pro). Opens Kiln's interactive inline 3D stage on the result (orbit/zoom panel in MCP Apps hosts; hosted sessions add a browser stage link).

INLINE 3D STAGE: on success this tool opens Kiln's interactive 3D stage — an inline viewer panel the user can orbit, zoom, and turn over — in hosts that render MCP Apps panels (Kiln's hosted connection attaches a browser stage link for hosts that don't). Oversized meshes are decimated automatically for the stage; the PNG preview is the floor, not the whole experience.

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": {
      "model_path": "<model_path>"
    },
    "name": "auto_add_rubber_feet"
  }
}

Input Schema

NameRequiredDescriptionDefault
num_feetNoNumber of feet to add (default 4). Default: 4.
model_pathYesPath to STL model.
output_pathNoOutput STL path. Auto-generated if omitted.
foot_height_mmNoHeight of each foot protrusion (default 1.5mm). Default: 1.5.
foot_diameter_mmNoDiameter of each foot pad (default 8mm). Default: 8.0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.5.1
    • changedInput schema / properties / foot_diameter_mm / description
      Previous value: -"Default: 8.0."New value: +"Diameter of each foot pad (default 8mm). Default: 8.0."
    • changedInput schema / properties / foot_height_mm / description
      Previous value: -"Default: 1.5."New value: +"Height of each foot protrusion (default 1.5mm). Default: 1.5."
    • addedInput schema / properties / model_path / description
      Added value: +"Path to STL model."
    • changedInput schema / properties / num_feet / description
      Previous value: -"Default: 4."New value: +"Number of feet to add (default 4). Default: 4."
    • addedInput schema / properties / output_path / description
      Added value: +"Output STL path. Auto-generated if omitted."
  2. Addedv1.5.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations only declare it is a non-destructive, non-open-world write; the description adds real behavioral context beyond that — it opens an interactive 3D stage on the result, attaches a browser link in hosted sessions, and auto-decimates oversized meshes for the stage. It does not disclose whether the input STL is preserved or a new file is written, nor any geometry constraints on foot placement, which keeps it below a 5.

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

Conciseness2/5

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

The core purpose is front-loaded in sentence one, but the 'INLINE 3D STAGE' paragraph restates the stage/link behavior already given in the preceding sentence, and the closing line ('the PNG preview is the floor, not the whole experience') is promotional filler. Roughly half the text is duplication rather than new information.

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?

With five well-documented parameters and no output schema, the description covers purpose and the notable side effect (stage opening, decimation), which is adequate. It leaves open whether the result is a modified copy of the input mesh and whether the feet are unioned geometry, details an agent would need before chaining this into a print pipeline.

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%, with each of the five parameters (num_feet, foot_height_mm, foot_diameter_mm, model_path, output_path) documented with defaults, so the baseline of 3 applies. The description adds nothing about parameter behavior — e.g. how num_feet interacts with foot diameter or what happens when output_path is omitted.

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 first sentence names a specific verb and resource ('Add rubber foot positions to model bottom') and flags the Pro tier requirement, so the agent knows exactly what geometry operation this performs. No sibling tool in the large list performs rubber-foot placement, so explicit differentiation is not strictly needed, but the description never says so.

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?

Usage is implied by 'model bottom' and the '(Pro)' tier marker, which signals an entitlement prerequisite. There is no explicit when-to-use guidance, no statement of preconditions (e.g. which faces count as the bottom, whether the model must be oriented), and no alternative or follow-up tool named.

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