Skip to main content
Glama
rokibul-mist

rhino-mcp

by rokibul-mist
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Hybrid

rhino_subd_torus

Creates a SubD torus primitive in Rhino at the specified center coordinates, using major and minor radii for outer and tube size. Use this to add torus geometry directly to the Rhino model.

Instructions

    Create a SubD torus primitive.
    
    Args:
    controller: RhinoController instance.
    x: X coordinate of center.
    y: Y coordinate of center.
    z: Z coordinate of center.
    major_radius: Torus major (outer) radius.
    minor_radius: Torus minor (tube) radius.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xNo
yNo
zNo
major_radiusNo
minor_radiusNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description is the only behavioral disclosure. It says the tool creates a SubD torus, which implies an additive document mutation, but it does not state orientation, current units, construction plane, or any effect beyond creation.

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?

The description is a single clear purpose line followed by a compact Args list. Every line adds information and the main purpose is front-loaded.

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 low-complexity primitive creation tool with an output schema, the parameter coverage is sufficient. However, with no annotations, the lack of orientation, units, insertion context, and usage guidance leaves the description only minimally complete.

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 0%, but the Args block defines all five schema parameters: x/y/z center coordinates and major/minor radii. The mention of a controller argument not present in the input schema slightly muddies the parameter mapping, so it loses one point.

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 opens with a specific action and object: 'Create a SubD torus primitive.' This clearly distinguishes it from the many sibling primitives, especially rhino_torus, by explicitly naming the SubD form.

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 context is only implied: if an agent wants a SubD torus, this tool fits. There is no explicit statement about when to prefer it over rhino_torus or rhino_cmd_torus, nor any exclusions or alternatives.

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

Install Server

Other Tools