Skip to main content
Glama
hellstein-dev

fusion-mcp

by hellstein-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

sheet_metal_create_flat_pattern

Create a flat pattern from a stationary face of a sheet metal body, returning its size, thickness, and bend list for manufacturing or documentation.

Instructions

Create the flat pattern of the component of a sheet metal body (one per component) and return its size, thickness and bends. The design workspace is active again afterwards.

Errors: a face of a non-sheet-metal body, an existing flat pattern without replace=true -> INVALID_PARAMS (the existing one is kept). replace=true is atomic: if the new flat pattern fails, the old one is recreated from its remembered stationary face. A flat pattern not made by this tool (or whose face changed) cannot be restored, so replace refuses it (INVALID_PARAMS reason=not_restorable, nothing changed) - delete it with sheet_metal_delete_flat_pattern first.

Returns {"component", "exists": true, "size_mm": [x, y], "thickness_mm", "bend_count", "bends": [{"angle_deg", "is_up"}], "replaced"}.

Input Schema

NameRequiredDescriptionDefault
replaceNoDelete the component's existing flat pattern first
stationary_faceYesFace of the sheet metal body that lies flat (e.g. the top)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations provided, the description carries the full behavioral burden and does so thoroughly: it discloses workspace side effects, INVALID_PARAMS error cases, atomic replacement behavior, and the fact that non-restorable patterns are refused and left unchanged.

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?

The description is front-loaded with the core action, then gives error behavior and return shape in a compact structure. Every sentence adds operational value, and the return object is stated efficiently.

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

Completeness5/5

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

Although there is no output schema and no annotations, the description provides the return fields, error cases, side effects, and replacement semantics. An agent has enough information to call the tool correctly and interpret the result.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds substantial meaning around replace=true, including atomicity and the not_restorable failure mode. It also clarifies the stationary_face requirement indirectly by describing replacement rollback from the remembered stationary face.

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?

The description states a specific verb and resource: create the flat pattern of a sheet metal body component. It also scopes the operation to one flat pattern per component, which distinguishes creation from retrieval or export siblings.

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?

It clearly explains the key replacement workflow: an existing flat pattern requires replace=true, and non-restorable existing patterns must be deleted first with sheet_metal_delete_flat_pattern. It does not explicitly route agents to sheet_metal_get_flat_pattern or export alternatives, but the main when/when-not conditions are present.

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