nx-ai-bridge

Overview Schema Source Related Servers Discussions Admin

revolve

Creates a body by sweeping all curves of a named sketch around an absolute axis, with optional start/end angles and boolean operations.

Instructions

Revolve all curves of a sketch about an axis given in ABSOLUTE coordinates. Units: millimetres (mm) and degrees.

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": {
      "sketch": "<sketch>",
      "axis_direction": "<axis_direction>"
    },
    "name": "revolve"
  }
}

Input Schema

Name	Required	Description	Default
`angle`	No	End angle in degrees.
`sketch`	Yes	Sketch name.
`target`	No	Target body for the boolean (body name or feature name). Required when boolean is not 'none' and the part has more than one body.
`boolean`	No	Boolean with an existing body: none = create a new body.	none
`axis_point`	No	A point on the axis. [x, y, z]
`start_angle`	No	Start angle in degrees.
`axis_direction`	Yes	Axis direction. [x, y, z]

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 13, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations exist, so the description carries the full burden. It usefully states that the axis is in ABSOLUTE coordinates and gives units, but says nothing about whether a new body is created, how the boolean/target parameters interact, what happens to the source sketch, or whether the operation is reversible — critical for a geometry-creation tool.

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?

Two tight sentences: operation and scope first, coordinate frame and units second. Nothing is redundant and the key qualifier (ABSOLUTE) is emphasized.

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

Completeness3/5

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

For a 7-parameter mutation tool with no annotations and no output schema, the description covers units and coordinate interpretation but leaves out the boolean/target workflow, failure modes, and result shape. Adequate minimum, but an agent could still invoke it incorrectly with a non-'none' boolean.

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 baseline is 3; the description earns an extra point by clarifying that the axis point and direction are interpreted in absolute (not sketch-local) coordinates and that linear units are millimetres while angles are degrees. It still does not explain the boolean/target relationship, but the coordinate-frame clarification is real value beyond the schema.

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?

"Revolve all curves of a sketch about an axis" names a specific operation and resource, and distinguishes the swept-entity scope (all curves) from a selective one. It does not contrast itself with siblings like extrude, but the verb+resource is unambiguous on its own.

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?

No when-to-use or when-not-to-use guidance, no prerequisites such as needing an existing sketch or closed profile, and no mention of alternatives. Only the implied context that a sketch must exist can be inferred from the parameter list.

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