Skip to main content
Glama
hellstein-dev

fusion-mcp

form_create_primitive

Creates a T-spline primitive body and control mesh in Fusion's Form environment for box, plane, cylinder, sphere, torus, or quadball shapes with set sizes and face counts.

Instructions

Create a T-spline primitive body (Form environment) with its control mesh.

Sizes per shape (numbers in units): box: x_size, y_size, z_size (x_faces, y_faces, z_faces); plane: x_size, y_size (x_faces, y_faces); cylinder: radius, height (radial_faces, length_faces); sphere: radius (longitude_faces, latitude_faces); torus: major_radius, minor_radius < major_radius (major_faces, minor_faces); quadball: radius (faces). Face counts default to Fusion's. A parameter of another shape -> INVALID_PARAMS.

T-spline primitives are NOT parametric: sizes are numbers, not expressions or user parameters (a string -> INVALID_PARAMS), and the body does not follow parameter changes. Shape it afterwards with form_move / form_crease / form_insert_edge, get a solid with form_convert_to_brep. Pull, Bridge, Fill Hole, Weld, Subdivide and the like have no Fusion API: read the TSM (form_get_tsm), edit it and create the body again (form_create_from_tsm).

Returns {"form": ref, "body": , "created_form": bool}; the body has a B-Rep ("brep_body") once Fusion regenerated it - a body without one fails (rolled back).

Example: form_create_primitive(shape="box", x_size=40, y_size=20, z_size=10, x_faces=4)

Input Schema

NameRequiredDescriptionDefault
formNoExisting form feature to add the body to (default: a new form feature)
nameNoName of the new body
facesNo
shapeYesbox, plane, cylinder, sphere, torus, quadball
unitsNoUnit of lengths and points (default mm)mm
heightNoNumber in `units`; expressions are not supported (not parametric)
originNoCorner of box / plane, centre of the others (default 0,0,0)
radiusNoNumber in `units`; expressions are not supported (not parametric)
x_sizeNoNumber in `units`; expressions are not supported (not parametric)
y_sizeNoNumber in `units`; expressions are not supported (not parametric)
z_sizeNoNumber in `units`; expressions are not supported (not parametric)
x_facesNo
y_facesNo
z_facesNo
symmetryNo{"x", "y", "z": bool} mirror symmetry, or "circular" (cylinder, sphere, torus)
componentNoComponent or occurrence for a new form feature (default: the root)
major_facesNo
minor_facesNo
x_directionNoLocal X axis (default [1,0,0])
y_directionNoLocal Y axis, perpendicular to X (default [0,1,0])
length_facesNo
major_radiusNoNumber in `units`; expressions are not supported (not parametric)
minor_radiusNoNumber in `units`; expressions are not supported (not parametric)
radial_facesNo
latitude_facesNo
longitude_facesNo
symmetric_facesNoFaces per symmetric segment (circular only)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

No annotations are provided, so the description carries the whole burden and does it well: it discloses non-parametric behavior ('body does not follow parameter changes'), that string expressions yield INVALID_PARAMS, that wrong-shape parameters yield INVALID_PARAMS, the return shape with created_form and brep_body, and that a body lacking a regenerated B-Rep fails and is rolled back. These are exactly the behavioral facts an agent needs and cannot get from annotations.

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-loaded with the one-line purpose, then a compact per-shape parameter table, then behavioral caveats, return contract, and a concrete example. Dense with zero filler despite covering a 27-parameter tool.

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?

For a high-parameter create tool with no annotations and no output schema, the description supplies the shape/param mapping, error conditions, return-value shape including brep_body and created_form, rollback behavior, and the follow-up editing path. Nothing material an agent needs before calling is missing.

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?

With 27 parameters and 63% schema coverage, the description adds real value by mapping which size/face parameters belong to each shape (box: x_size/y_size/z_size + x/y/z_faces, torus: major_radius/minor_radius with the minor < major constraint, etc.) and by warning that sizes are numbers in `units` rather than expressions. It does not explain symmetry, origin/direction conventions, component, or form, leaving those to the schema's own descriptions.

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 T-spline primitive body (Form environment) with its control mesh.' This immediately distinguishes it from siblings like form_create_from_tsm (rebuild from TSM data) and form_convert_to_brep (conversion). No ambiguity about what the tool produces.

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

Usage Guidelines5/5

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

Explicitly routes the agent: shape it afterwards with form_move / form_crease / form_insert_edge, convert with form_convert_to_brep, and for operations Fusion has no API for (Pull, Bridge, Fill Hole, Weld, Subdivide) read the TSM via form_get_tsm and recreate. That is explicit when-to-use-this vs when-to-use-alternatives guidance.

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