nx-ai-bridge

Overview Schema Source Related Servers Discussions Admin

create_cylinder

Creates a cylinder from a base-center origin, axis direction, diameter, and height in millimetres; optionally unite, subtract, or intersect it with an existing body.

Instructions

Create a cylinder. origin is the centre of the base circle; the cylinder grows along direction. 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": {
      "diameter": "<diameter>",
      "height": "<height>"
    },
    "name": "create_cylinder"
  }
}

Input Schema

Name	Required	Description	Default
`height`	Yes	Height (mm).
`origin`	No	Centre of the base. [x, y, z]
`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
`diameter`	Yes	Diameter (mm).
`direction`	No	Axis direction. [x, y, z]

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 13, 2026

TDQS

B3.3/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose the key behavioral facts: origin is the base-circle centre and growth follows direction, plus the units. It omits whether a part must be open, whether a new body is created by default, error behavior, and the boolean side effects (subtract destroys material).

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 short sentences; the geometric anchor is front-loaded before the unit convention. No filler or redundancy.

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 6-parameter CAD primitive with no annotations and no output schema, the geometry and units are covered but prerequisites, boolean side effects, and target-selection rules are left entirely to the schema. Adequate but with clear gaps.

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

Parameters3/5

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

Schema description coverage is 100%, so baseline is 3. The description adds genuine value for origin (base circle centre rather than arbitrary point) and direction (growth axis) plus the global mm/degree unit convention, but adds nothing for boolean, target, diameter, or height 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?

States a specific verb+resource ("Create a cylinder") and clarifies the geometric semantics of origin and direction. It does not explicitly distinguish itself from siblings like create_cone or create_sphere, but the primitive named is unambiguous.

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 guidance, no prerequisites (e.g. an open part or active body), and no routing to sibling creation tools or to boolean_unite/boolean_subtract. The tool name is the only usage signal.

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