MCP server connecting Claude to McNeel Rhino 8 and Grasshopper via rhino3dm and an in-Rhino bridge plugin.
rhino-mcp exposes 29 tools with inconsistent quality. Most tools have basic descriptions (50-150 chars) and input schemas, but lack depth in parameter documentation and output schema specification. Many tools (e.g., rhino.annotation.dim_linear, rhino.annotation.contour) have empty input schemas with no parameters, making their purpose unclear. Parameter descriptions are minimal, e.g., 'First point' for point_a lacks format guidance. No tool documents return types or output structure. Error handling is absent from descriptions. Tool naming is reasonable (verb_noun pattern) but some names are vague (e.g., 'invoke' commands like dim_linear, contour). Batch tool (rhino.batch.modify) lacks clarity on object specification format. BIM tools (export_ifc, import_ifc) have better descriptions but still omit output schema details.
Calculate area of a Brep or Mesh object
Calculate bounding box of objects
Invoke contour command
Calculate curvature of a curve at parameter t
Calculate distance between two points
Activate draft angle analysis
Probe ray intersections with Breps in the document
Create section curves from objects intersected with a plane
8 tools have empty input schemas (no parameters defined): draft_angle, contour, zebra, dim_linear, dim_aligned, dim_angular, leader, hatch. These are interactive commands that require user input but expose no parameters, making LLM invocation impossible without UI interaction.
Parameter descriptions lack format guidance and constraints. E.g., point_a/point_b described as 'First point' without specifying format (array [x,y,z]? object {x,y,z}?). plane_normal defaults to Z-axis but format is undocumented. LLMs cannot infer correct input structure.
Inferred effective spec: 2026-07-28+.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 49 | 2026-07-28+ | v2 |
Calculate volume of a Brep or Mesh object
Activate zebra analysis
Place callout annotation with leader
Add clipping plane annotation
Invoke aligned dimension command
Invoke angular dimension command
Invoke linear dimension command
Invoke hatch command
Invoke leader command
Place north arrow annotation on drawing
Place revision cloud annotation
Place scale bar annotation on drawing
Add text annotation to document
Add text dot annotation
Apply transform and attribute changes to many objects in a single call
Export to gbXML format
Export objects to IFC format with optional entity type mapping
Import IFC file and bucket objects by entity type
Tag objects with IFC entity type and PropertySet metadata
Read PropertySet metadata from an object
Write PropertySet metadata to an object
No tool documents output schema or return type. LLMs cannot plan downstream calls or extract required fields. E.g., does bounding_box return {min, max} or {x_min, y_min, z_min, x_max, y_max, z_max}? Does probe_intersection return hit coordinates?
rhino.batch.modify description lacks clarity on 'object specifications' format. Parameter 'objects' is an array but structure is undefined, does each item have {id, transform, attributes}? How are modifications specified? Ambiguity forces LLM guessing.
No error handling guidance in any tool description. LLMs cannot distinguish retryable errors from user-fixable ones. E.g., if import_ifc fails due to invalid file path vs. unsupported IFC schema, what should the agent do?