Skip to main content
Glama
formastep-mcp
by eldertek

export_manufacturing_bundle

Idempotent

Compile PartSpec models, validate STEP and DFM, then export a manufacturing bundle with a SHA-256 manifest for traceable production handoff.

Instructions

Compile PartSpec, validate STEP + DFM, and export a full manufacturing bundle with SHA-256 manifest.

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

Input Schema

NameRequiredDescriptionDefault
specYes
processNo
output_dirNobundle

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already state that this is non-read-only, idempotent, closed-world, and non-destructive, so the safety profile is mostly covered. The description adds useful behavior detail by mentioning STEP + DFM validation and a SHA-256 manifest, but it does not disclose overwrite behavior, file-write scope, or failure handling for the output bundle.

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?

A single compact sentence with the main operations front-loaded and no wasted wording. It is appropriately sized for a tool summary, though that concision contributes to the parameter gaps.

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?

This is a complex compile/validate/export tool with a nested spec object and three parameters, and the description leaves major input semantics undocumented. The presence of an output schema reduces the need to describe return values, but the input side remains incomplete.

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 description coverage is 0%, so the description must explain the three parameters. It mentions PartSpec but does not explain the spec object structure, the process enum choices, or the purpose and overwrite implications of output_dir.

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 gives a specific verb chain and resource: compile PartSpec, validate STEP + DFM, and export a manufacturing bundle. This clearly distinguishes it from dfm_audit, part_build, and step_inspect, though it does not explicitly name those 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?

Usage is implied: use this when the end goal is a full manufacturing bundle rather than a standalone audit, build, or inspection. However, there is no explicit when-to-use or when-not-to-use guidance, and no alternative is named.

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