Skip to main content
Glama
hellstein-dev

fusion-mcp

sheet_metal_create_rule

Copies a base sheet metal rule and sets thickness, bend radius, K-factor, and relief values to define a custom design rule, which stays inactive until assigned.

Instructions

Create a design sheet metal rule by copying a base rule and setting values.

Units: a plain number is in units (default mm); a string is a Fusion expression and may use Thickness ("Thickness * 1.5") - write units in expressions ("2 mm"), a rule in inches reads bare numbers as inches. The rule is not used until sheet_metal_assign_rule or the rule argument of a flange tool.

Errors: name already in the design, k_factor outside 0..1, a negative length -> INVALID_PARAMS; unknown base_rule -> ENTITY_NOT_FOUND. On any error no rule is left.

Returns {"rule": , "base": {"name", "source"}}.

Example: sheet_metal_create_rule(name="Steel 2mm", thickness=2, bend_radius="Thickness * 1", k_factor=0.44, relief_shape="round")

Input Schema

NameRequiredDescriptionDefault
gapNoGap at corners / rips
nameYesNew design rule name (unique)
unitsNoUnit of plain-number lengths (default mm)mm
k_factorNoK-factor 0..1 for the flat pattern
base_ruleNoRule to copy (default: the library default rule)
thicknessNoSheet thickness
base_sourceNoWhere to look for base_ruleall
bend_radiusNoBend radius; e.g. 'Thickness * 1'
relief_depthNoBend relief depth
relief_shapeNostraight, tear or round bend relief
relief_widthNoBend relief width
relief_remnantNoBend relief remnant

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does well: it documents unit interpretation, expression behavior, error cases (duplicate name, k_factor range, negative length, unknown base_rule), atomicity (no rule left on error), and return shape. It does not mention permissions or rate limits, but covers the main behavior an agent needs.

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?

Front-loads the core purpose, then presents units, errors, return value, and an example in a compact, scannable structure. Every section adds useful information for a 12-parameter creation tool, with no filler.

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?

Given 12 parameters, no annotations, and no output schema, the description is complete enough for correct invocation: it explains units and expressions, error conditions and atomicity, the follow-up assignment step, and the return shape. The schema provides per-parameter details, and the description supplements them with behavioral context.

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 schema already defines all parameters. The description adds valuable cross-parameter semantics about plain numbers using units, strings as Fusion expressions, and how bare numbers are interpreted when a rule uses inches, plus an example that clarifies invocation.

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: create a design sheet metal rule by copying a base rule and setting values. It also distinguishes the new rule from assignment, noting that the rule is not used until sheet_metal_assign_rule or a flange tool's rule argument is used.

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?

Clearly explains that the tool creates a rule and that the rule must then be assigned via sheet_metal_assign_rule or a flange tool. It gives strong context but does not explicitly say when to create a new rule versus use an existing rule from sheet_metal_list_rules.

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