rhino-mcp

Overview Schema Source Related Servers Score Discussions Admin

rhino_subd_box

Create a SubD box primitive in Rhino by specifying base corner coordinates, length, width, height, and face counts per axis.

Instructions

    Create a SubD box primitive.
    
    Args:
    controller: RhinoController instance.
    x: X coordinate of base corner.
    y: Y coordinate of base corner.
    z: Z coordinate of base corner.
    length: Box length along X.
    width: Box width along Y.
    height: Box height along Z.
    face_x: Number of faces along X.
    face_y: Number of faces along Y.
    face_z: Number of faces along Z.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`x`	No
`y`	No
`z`	No
`width`	No
`face_x`	No
`face_y`	No
`face_z`	No
`height`	No
`length`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 9, 2026

TDQS

A3.8/5.0

Behavior2/5

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

With no annotations provided, the description carries the burden of behavioral disclosure, but it only says 'Create' and lists args. It does not state whether the box is inserted into the active document, how the controller is used, what units or coordinate system apply, or what side effects occur. The extra 'controller' arg is also unexplained for MCP callers.

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?

A single purpose sentence is front-loaded, followed by a compact, scannable Args list where every line carries parameter meaning. There is no redundant explanation or filler.

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?

All nine callable parameters are defined and an output schema exists, so the agent can invoke the tool and understand the return shape. The description falls short only in non-schema context such as explicit alternative routing and side-effect or insertion behavior, which are addressed in other dimensions.

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?

Every schema parameter (x, y, z, length, width, height, face_x, face_y, face_z) gets a one-line semantic explanation, such as 'length: Box length along X', fully compensating for the 0% schema description coverage. One deduction: the description also lists a 'controller' argument not present in the input schema, which could confuse an agent about invocation.

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 opening sentence 'Create a SubD box primitive' names a specific verb and resource, and the 'SubD' qualifier differentiates it from sibling primitives like rhino_box and rhino_mesh_box. The subsequent parameter list reinforces that it creates a box, not another shape.

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 obviously for creating a SubD box, so an agent can infer that context. However, it never explicitly contrasts with rhino_box, rhino_mesh_box, or other SubD primitives, nor states exclusions such as 'use rhino_box for NURBS boxes.'

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

Install Server