nx-ai-bridge

Overview Schema Source Related Servers Discussions Admin

create_cone

Creates a cone or truncated cone from base diameter, height, and optional top diameter, positioned at a specified origin in millimetres and degrees.

Instructions

Create a cone or truncated cone. origin is the centre of the base circle. 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": {
      "base_diameter": "<base_diameter>",
      "height": "<height>"
    },
    "name": "create_cone"
  }
}

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
`direction`	No	Axis direction. [x, y, z]
`top_diameter`	No	Diameter at the top (mm); 0 for a sharp cone.
`base_diameter`	Yes	Diameter at the base (mm).

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?

With no annotations, the description must carry behavioral disclosure; it establishes that the call produces geometry and clarifies the origin reference point and units, which are genuinely useful. However, it omits whether a new body is created by default, what happens when boolean is set, and any permission or state prerequisites.

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?

Three short sentences, front-loaded with the core action, then the non-obvious origin semantics, then 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?

Seven parameters, one enum, no annotations and no output schema – the description covers the most ambiguous parameter (origin) and units but ignores the boolean/target interaction, which is the highest-risk aspect of this tool. Adequate but with a meaningful gap.

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 the baseline is 3. The description re-states that origin is the centre of the base circle (schema says 'Centre of the base') and adds the millimetre/degree unit convention, a modest addition 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?

The description names a specific verb and resource ('Create a cone or truncated cone') and even disambiguates the variant via the truncated-cone case, which maps to top_diameter. It does not explicitly contrast with siblings like create_cylinder or create_sphere, but the resource naming makes the distinction obvious.

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, when-not-to-use, or alternatives are given. An agent gets no guidance on choosing between this tool's built-in boolean options and the standalone boolean_unite/boolean_subtract/boolean_intersect tools, nor on prerequisites such as having an open part.

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