Skip to main content
Glama
formastep-mcp
by eldertek

part_build

Idempotent

Compile a parametric PartSpec JSON dictionary into STEP, 3MF, STL, or SVG artifacts for CAD and manufacturing workflows.

Instructions

Compile a parametric PartSpec JSON dict and export STEP/3MF/STL/SVG artifacts.

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": {
      "spec": "<spec>"
    },
    "name": "part_build"
  }
}

Input Schema

NameRequiredDescriptionDefault
specYes
formatsNo
output_dirNoout

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnly=false, idempotent=true, destructive=false, and openWorld=false, so the safety profile is covered. The description adds useful context that artifacts are written out (implying filesystem output alongside output_dir), but says nothing about overwrite behavior, where files land, or what happens on an invalid spec.

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?

A single dense sentence with the action and outputs front-loaded and no filler. It is efficient, though the density comes at the cost of leaving key semantics unstated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with a nested, schema-undocumented spec object, the description should explain at least the shape or source of a PartSpec and the meaning of output_dir and format defaults. An output schema exists, so return values needn't be covered, but the input side is substantially underspecified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the 'spec' parameter is a free-form nested object with additionalProperties=true, so the schema gives an agent no structural guidance at all. The description names the concept ('PartSpec JSON dict') and lists four formats, but omits stl_ascii from the schema's enum and never explains output_dir or what a valid spec contains.

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 pair ('Compile' and 'export') with a clear resource ('parametric PartSpec JSON dict') and enumerates the artifact types produced. This distinguishes it from siblings like step_inspect or dfm_audit by action, though it never explicitly names a sibling to contrast against.

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?

There is no statement of when to choose this tool over export_manufacturing_bundle or view_render_svg, and no prerequisites (e.g., that a valid PartSpec must exist or that geometry is generated rather than inspected). Usage is only inferable from the verb 'compile'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.