Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

estimate_supports

Read-only

Analyze an STL or OBJ mesh for overhangs and estimate the support material volume required to 3D print it in its current orientation.

Instructions

Estimate support volume for a 3D model.

        Analyzes the mesh for overhangs and estimates the volume of
        support material needed to print the model in its current
        orientation.

        Args:
            file_path: Path to an STL or OBJ mesh file.
            max_overhang_angle: Maximum overhang angle in degrees
                before supports are needed (default 45).

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": {
      "file_path": "<file_path>"
    },
    "name": "estimate_supports"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_pathYesPath to an STL or OBJ mesh file.
max_overhang_angleNoMaximum overhang angle in degrees before supports are needed (default 45). Default: 45.0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.5.1
    • addedInput schema / properties / file_path / description
      Added value: +"Path to an STL or OBJ mesh file."
    • changedInput schema / properties / max_overhang_angle / description
      Previous value: -"Default: 45.0."New value: +"Maximum overhang angle in degrees before supports are needed (default 45). Default: 45.0."
  2. Changed2 schema fields changedv1.5.0
    • removedInput schema / properties / max_overhang_angle / default
      Removed value: -45
    • addedInput schema / properties / max_overhang_angle / description
      Added value: +"Default: 45.0."
  3. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful context by explaining that it analyzes mesh overhangs and depends on the model's current orientation, but it does not disclose return units, precision, performance characteristics, or limitations.

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 short and front-loads the main purpose, then explains the analysis and parameters. The Args block duplicates the schema and could be removed, but the overall wording is efficient and not verbose.

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 simple two-parameter estimation tool, the description covers the purpose, inputs, and orientation dependence. However, with no output schema it does not specify the return value's units or format, leaving some ambiguity about how to interpret the estimated support volume.

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%, so the schema already documents both parameters. The description's Args section simply repeats the same file_path and max_overhang_angle explanations without adding syntax, format, or behavioral meaning beyond the schema.

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: estimating support volume for a 3D model by analyzing the mesh for overhangs. It is clear what the tool does, but it does not distinguish this tool from closely related siblings such as estimate_support_material or plan_supports.

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 implies the tool is used before printing to estimate support material in the current orientation, but it gives no explicit when-to-use guidance, no prerequisites, and no alternatives for related tasks like support planning or broader printability analysis.

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