Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

step_file_info

Read-only

Extract metadata from a STEP file without converting it to preview product names, body count, and schema, so you can inspect a file before importing.

Instructions

Extract metadata from a STEP file without converting it.

        Parses the STEP ASCII header to extract product names, estimated
        body count, file schema, and other metadata.  This is fast and
        requires no external backend.

        Use this to inspect a STEP file before deciding whether to
        import it.

        Args:
            file_path: Path to the STEP/STP file.

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": "step_file_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_pathYesPath to the STEP/STP file.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.1
    • addedInput schema / properties / file_path / description
      Added value: +"Path to the STEP/STP file."
  2. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish readOnly/closed-world/non-destructive, so the description's added value is the implementation note: it only parses the ASCII header, needs no external backend, and is fast. That also hints the metadata (body count) is an estimate rather than a full geometry read — useful for trusting results. It does not mention failure behavior for non-STEP or malformed files.

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 behavioral and when-to-use statements are front-loaded in three tight sentences. The trailing 'Args:' section duplicates the input schema and does not earn its space, which keeps it from a 5.

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 no output schema, the description does list the primary returned fields (product names, body count, file schema, 'other metadata'), which covers the essentials. However, the return shape, ordering, and behavior on files with missing headers are unstated, leaving moderate gaps for a tool whose whole value is its output.

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 coverage is 100% and the single parameter is already documented as 'Path to the STEP/STP file.' The 'Args:' block merely restates that text, adding no path-resolution, extension, or relative-vs-absolute guidance beyond the schema. Baseline 3 applies when the schema does all the work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Extract metadata from a STEP file') and immediately scopes it with 'without converting it', which separates it from the sibling import_step_file. The agent can tell what it gets (product names, body count, schema) without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Use this to inspect a STEP file before deciding whether to import it' gives a concrete decision-point context and implicitly routes to import_step_file afterwards. It stops short of naming import_step_file or check_step_support explicitly, so the alternative routing is left to inference.

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