rhino-mcp

Overview Schema Source Related Servers Score Discussions Admin

rhino_cmd_torus

Create a torus in Rhino by providing center coordinates, major radius, and minor radius, enabling programmatic 3D modeling through MCP.

Instructions

    Create a torus in Rhino.
    
    Args:
    controller:    RhinoController instance.
    x, y, z:       World-space center of the torus.
    major_radius:  Distance from the torus center to the tube center.
    minor_radius:  Radius of the tube cross-section.
    
    Returns:
    Dict with 'status' and 'command' keys.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`x`	No
`y`	No
`z`	No
`major_radius`	No
`minor_radius`	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

B3.1/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden. It reveals the return shape ('Dict with status and command keys'), hinting at a command-generation pattern, but it does not state whether the command executes immediately, what status values occur, whether the operation is undoable, or what side effects on the Rhino document occur beyond the obvious creation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and scannable with clear Args and Returns sections, front-loading the core purpose in the first sentence. It contains no filler, repetition, or irrelevant detail.

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 simple five-parameter creation tool with defaults on everything, the description covers the essentials, and the status/command return disclosure is useful. But it leaves open how the returned command is consumed, when to prefer this over rhino_torus or rhino_subd_torus, and radius validity constraints, which matters more given there are zero annotations.

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 description coverage is 0%, and the description compensates by explaining every parameter: coordinates are 'World-space center', and the two radii are defined in geometric terms the schema lacks. Minor gaps: the 'controller' argument is mentioned but absent from the schema, and no positivity constraints are given for the radii.

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 ('Create a torus in Rhino') and adds meaningful geometric definitions for the radii (major radius as center-to-tube-center distance, minor radius as tube cross-section radius). However, it does not differentiate from sibling tools rhino_torus and rhino_subd_torus, leaving the agent to infer which variant this is.

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?

The description contains no guidance on when to use this tool versus alternatives. There are no exclusions, prerequisites, or selection criteria to distinguish it from rhino_torus or rhino_subd_torus, so an agent scanning the sibling list gets no decision signal.

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

Install Server