Skip to main content
Glama
rokibul-mist

rhino-mcp

by rokibul-mist
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Hybrid

rhino_subd_cylinder

Create a SubD cylinder primitive in Rhino. Specify base center (x, y, z), radius, and height to generate the shape for modeling.

Instructions

    Create a SubD cylinder primitive.
    
    Args:
    controller: RhinoController instance.
    x: X coordinate of base center.
    y: Y coordinate of base center.
    z: Z coordinate of base center.
    radius: Cylinder radius.
    height: Cylinder height.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xNo
yNo
zNo
heightNo
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
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 behavioral burden. It only restates that a SubD cylinder is created and lists parameters; it does not disclose axis/orientation, capping behavior, units, object placement scope, or return 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 compact and uses a clear parameter-list structure with no padding. It loses a point because it mentions a 'controller' argument that is not present in the input schema, which could slightly confuse an agent.

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?

For a simple primitive-creation tool with an output schema present, the parameter documentation is sufficient to invoke the tool correctly. Minor gaps remain around orientation and SubD-specific creation behavior, but these are not critical for basic usage.

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%, but the description compensates fully by explaining every schema parameter: x/y/z as base-center coordinates, radius, and height. This adds semantic meaning well beyond the schema's names and defaults.

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 states a clear, specific action: 'Create a SubD cylinder primitive.' The 'SubD' qualifier distinguishes it from the analogous NURBS tool rhino_cylinder, and the resource is unambiguous.

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 guidance is given about when to use this tool versus alternatives such as rhino_cylinder, rhino_subd_sphere, or other SubD primitives. There are no conditions, prerequisites, or exclusions stated.

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