Skip to main content
Glama
nx-ai-bridge

nx-ai-bridge

by qiuyekai

create_block

Creates a rectangular NX block from length, width, and height in millimetres at an origin corner, with optional boolean unite, subtract, or intersect against an existing body.

Instructions

Create a rectangular block. origin is the corner with the smallest x/y/z; the block extends length along +X, width along +Y, height along +Z. 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": {
      "length": "<length>",
      "width": "<width>",
      "height": "<height>"
    },
    "name": "create_block"
  }
}

Input Schema

NameRequiredDescriptionDefault
widthYesSize along Y (mm).
heightYesSize along Z (mm).
lengthYesSize along X (mm).
originNoCorner point. [x, y, z]
targetNoTarget body for the boolean (body name or feature name). Required when boolean is not 'none' and the part has more than one body.
booleanNoBoolean with an existing body: none = create a new body.none

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does add useful behavior: the origin is the minimum corner, dimensions extend along +X/+Y/+Z, and units are millimetres and degrees. However, it does not say which part receives the new block, whether the operation is reversible, what errors occur for invalid boolean/target combinations, or what the tool returns.

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 front-loaded sentences with no waste. The core operation comes first, followed by the coordinate-frame and unit details an agent needs to place the block correctly.

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 six-parameter creation tool with no annotations and no output schema, the definition covers the geometry and units well and the schema covers all parameters. It remains incomplete on execution context and results: it does not state where the block is created, how conflicts with existing bodies are handled beyond the boolean field, or what identifier or object is returned.

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 already 100%, so the baseline is 3, but the description adds real meaning beyond the schema by defining origin as the corner with the smallest x/y/z and mapping length, width, and height to +X, +Y, and +Z respectively. It also reinforces the millimetre/degree units, which helps an agent interpret the numeric parameters correctly.

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?

The description states a specific verb and resource: 'Create a rectangular block.' The rectangular block shape is clearly distinguishable from sibling creation tools such as create_cone, create_cylinder, and create_sphere.

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?

It explains the geometry of the block but gives no guidance on when to choose this tool versus alternatives such as create_sketch, extrude, or the boolean_* tools. The boolean parameter's behavior is described, but that is parameter semantics rather than tool-selection guidance.

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