Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

export_step

Export a design as a STEP file with real analytic B-rep geometry for CAD handoff; specify the design ID and optionally an output directory.

Instructions

Export a design as a STEP file — real analytic B-rep, always.

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": {
      "design_id": "<design_id>"
    },
    "name": "export_step"
  }
}

Input Schema

NameRequiredDescriptionDefault
design_idYesThe design to export (see ``list_designs``).
output_dirNoOptional directory for the exported file; defaults to a fresh Kiln work directory. Default: "".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.5.1
    • addedInput schema / properties / design_id / description
      Added value: +"The design to export (see ``list_designs``)."
    • changedInput schema / properties / output_dir / description
      Previous value: -"Default: \"\"."New value: +"Optional directory for the exported file; defaults to a fresh Kiln work directory. Default: \"\"."
  2. Addedv1.5.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the write-but-safe profile is covered. The description adds one real behavioral trait beyond that: the output is 'real analytic B-rep, always', i.e. true analytic geometry rather than a tessellated approximation. It does not address overwrite behavior or whether an existing file at output_dir is replaced.

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?

One front-loaded sentence with the action first and the fidelity guarantee as a trailing qualifier. No wasted words; every clause carries 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?

For a simple two-parameter tool this is close, but with no output schema the description never says what is returned (e.g. the resulting file path) or how an agent locates the exported artifact. The schema covers the input side, but the output side is undocumented anywhere.

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?

Both parameters are documented at 100% schema coverage, including the design_id cross-reference to list_designs and the output_dir default, so the description adds nothing parameter-specific. Baseline 3 is appropriate when the schema carries the load.

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: export a design to a STEP file. The format naming implicitly separates it from export_model_3mf, but no sibling (check_step_support, step_file_info, import_step_file) is named explicitly, so an agent must infer the boundary itself.

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 gives no when-to-use guidance at all. It never says when STEP is preferred over 3MF export, nor that check_step_support or step_file_info exist as prerequisites/companions, leaving the agent to guess from names alone.

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