Skip to main content
Glama
rokibul-mist

rhino-mcp

by rokibul-mist
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Hybrid

rhino_cmd_spiral

Creates a conical spiral curve in Rhino from a start point, with specified pitch, turns, and start/end radii.

Instructions

    Create a spiral (conical helix) curve in Rhino.
    
    Rhino Spiral prompts: axis start -> axis end -> start radius -> end radius.
    We place the axis start at (x, y, z) and axis end at (x, y, z + pitch*turns).
    
    Args:
    controller:    RhinoController instance.
    x, y, z:       Base point (axis start).
    pitch:         Vertical distance per turn.
    turns:         Number of full turns.
    start_radius:  Radius at the base of the spiral.
    end_radius:    Radius at the top of the spiral.
    
    Returns:
    Dict with 'status' and 'command' keys.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xYes
yYes
zYes
pitchNo
turnsNo
end_radiusNo
start_radiusNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations provided, the description carries the burden of explaining behavior. It does disclose the axis placement formula and the prompt sequence, which adds some transparency, but it does not mention side effects like creating a document object, coordinate system expectations, or failure behavior.

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 organized into purpose, prompt context, formula, argument list, and return value, making it easy to scan. The 'Rhino Spiral prompts' line is mildly redundant but still useful context; overall, the structure is efficient and front-loaded.

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?

The description provides the essential formula and parameter semantics needed to call the tool, and the output schema covers the return structure. It lacks usage guidance relative to sibling tools and does not address units, but for a curve-creation tool with this schema, it is reasonably complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must fully explain the parameters. It does: every parameter is listed with a concise meaning, including the relationship between pitch and turns in the axis-end calculation. This goes well beyond the bare schema and gives an agent enough understanding to set values correctly.

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 clearly states 'Create a spiral (conical helix) curve in Rhino' with a specific verb and resource. It is mostly clear, but sibling tools like rhino_spiral and rhino_helix exist, and the description does not differentiate this tool from them.

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 explains how the spiral is constructed but provides no guidance on when to use this tool versus alternatives such as rhino_spiral, rhino_helix, or rhino_cmd_helix. It does not mention exclusions, prerequisites, or scenarios where another tool would be more appropriate.

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