Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

auto_recess_pocket

Adds a recessed pocket to a chosen face of an STL model, creating a rim for bed-safe decoration.

Instructions

Add recessed pocket to a face for bed-safe decoration (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": {
      "model_path": "<model_path>"
    },
    "name": "auto_recess_pocket"
  }
}

Input Schema

NameRequiredDescriptionDefault
faceNoWhich face to recess: ``"bottom"`` (the default), ``"top"``, ``"front"``, ``"back"``, ``"left"`` or ``"right"``. Default: "bottom".
model_pathYesPath to STL model.
output_pathNoOutput STL path. Auto-generated if omitted.
pocket_depth_mmNoHow deep the pocket should be (default 1.2mm). Default: 1.2.
pocket_inset_mmNoRim width around the pocket edge (default 3mm). Default: 3.0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.5.1
    • changedInput schema / properties / face / description
      Previous value: -"Default: \"bottom\"."New value: +"Which face to recess: ``\"bottom\"`` (the default), ``\"top\"``, ``\"front\"``, ``\"back\"``, ``\"left\"`` or ``\"right\"``. Default: \"bottom\"."
    • addedInput schema / properties / model_path / description
      Added value: +"Path to STL model."
    • addedInput schema / properties / output_path / description
      Added value: +"Output STL path. Auto-generated if omitted."
    • changedInput schema / properties / pocket_depth_mm / description
      Previous value: -"Default: 1.2."New value: +"How deep the pocket should be (default 1.2mm). Default: 1.2."
    • changedInput schema / properties / pocket_inset_mm / description
      Previous value: -"Default: 3.0."New value: +"Rim width around the pocket edge (default 3mm). Default: 3.0."
  2. Addedv1.5.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already disclose readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds the intended use ("bed-safe decoration") and a Pro-tier signal, but does not describe whether the original model is modified, what output is produced, or any geometric constraints.

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 a single front-loaded sentence with no filler. It could be slightly more informative about the operation's result, but every word currently earns its place.

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 mesh-modifying tool with five parameters, the annotations and fully documented schema carry most of the load. The description still leaves gaps around output behavior, whether the source is modified in place, and practical constraints on pocket dimensions or face selection.

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 the schema itself documents the face options, depth default, inset default, and output path behavior. The description adds no parameter meaning beyond what the schema already provides, so the baseline of 3 is appropriate.

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 states a specific verb and resource: "Add recessed pocket to a face." It also gives a purpose ("bed-safe decoration") and a tier hint ("Pro"), so the action is clear, though it does not explicitly distinguish this tool from the many other decoration and mesh-modification siblings.

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 phrase "for bed-safe decoration (Pro)" implies when to use it, but there are no explicit exclusions, prerequisites, or named alternatives among sibling tools. An agent can infer the general context but must guess when a different decoration tool is more appropriate.

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