nx-ai-bridge

Overview Schema Source Related Servers Discussions Admin

extrude

Creates solid geometry from closed sketch loops by pulling them along the sketch normal or a specified direction, with optional boolean operations.

Instructions

Extrude all curves of a sketch along the sketch normal (or direction). The curves must form closed loops to get a solid. 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>",
      "distance": "<distance>"
    },
    "name": "extrude"
  }
}

Input Schema

Name	Required	Description	Default
`start`	No	Start distance (mm).
`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
`distance`	Yes	End distance (mm) measured from the sketch plane. Negative extrudes the other way.
`direction`	No	Extrude direction; default is the sketch normal. [x, y, z]

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 13, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It discloses the default direction (sketch normal), the closed-loop requirement for producing a solid, and the unit conventions, but says nothing about whether a new body is always created by default, what happens with open loops, or what the call returns. For a mutation tool with zero annotation coverage this is helpful but incomplete.

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 sentences, front-loaded with the operation and followed by the key precondition. No redundant restatement of the tool name and nothing that could be cut without losing meaning.

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

Completeness4/5

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

For a six-parameter geometry mutation with no annotations and no output schema, the description covers the operation, the geometric precondition, and units. The remaining gaps are secondary: what body is produced by default and how boolean/target interact are left entirely to the schema.

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 all six parameters are already documented, including the default-normal behavior and negative distance direction. The description adds only the unit convention (mm, degrees), which is genuinely useful but marginal; baseline 3 applies.

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?

The description states a specific verb and resource ('Extrude all curves of a sketch') plus the axis of extrusion (sketch normal or direction), so the operation is unambiguous. It stops short of naming a sibling such as revolve to differentiate when extrusion is the right choice, so it lands at 4 rather than 5.

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

Usage Guidelines3/5

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

Usage is only implied: the tool is for turning sketch curves into solids. The description does give one real precondition ('curves must form closed loops to get a solid'), which tells the agent when the call will succeed. There is no explicit when-to-use versus revolve or when-not guidance.

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