Rhino integration through the Model Context Protocol
RhinoMCP has 11 tools with basic schemas and descriptions, but significant gaps limit production readiness. Tool names follow verb_noun convention (create_object, delete_object, get_document_info), which is good. However, descriptions are often generic (e.g., 'Create a new object in the Rhino document', 10-15 chars above minimum but lacking context on WHEN to use or prerequisites). Parameter descriptions exist but are sparse: 'type' lacks enum constraints despite accepting only 6 values; 'params' is a free-form object with no guidance on type-specific structure. Output schemas are not documented, callers don't know what fields to expect from create_object or get_object_info. Error handling is absent: no guidance on retryability, user-fixable vs fatal errors, or recovery paths. The execute_rhinoscript_python_code tool is a major security red flag, arbitrary code execution with no validation, permission gates, or audit trail. Batch tools (create_objects, modify_objects) exist but lack pagination/limit guidance. No tool annotations (readOnlyHint, destructiveHint) despite clear risk levels assigned.
Create a new object in the Rhino document.
Create multiple objects at once in the Rhino document.
Delete an object from the Rhino document.
Execute arbitrary RhinoScript code in Rhino.
Get detailed information about the current Rhino document
Get detailed information about a specific object in the Rhino document. You can either provide the id or the object_name of the object to get information about. If both are provided, the id will be used.
Return the RhinoScriptsyntax for a specific category.
execute_rhinoscript_python_code allows arbitrary code execution with zero validation, permission gates, or audit trail. This is a critical security vulnerability.
Output schemas are not documented for any tool. Callers cannot know what fields to expect from create_object, get_object_info, or get_document_info. This forces LLMs to guess and wastes tokens on trial-and-error.
Parameter 'type' in create_object accepts only 6 values (POINT, LINE, POLYLINE, CURVE, BOX, SPHERE) but is defined as free-form string with no enum constraint. LLMs will hallucinate invalid types.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 40 | <=2025-11-25 | v2 |
Get detailed information about the currently selected objects in Rhino
Modify an existing object in the Rhino document.
Create multiple objects at once in the Rhino document.
Select objects in the Rhino document.
Parameter 'params' in create_object is a free-form object with no guidance on type-specific structure. Description says 'Type-specific parameters dictionary' but does not explain what keys/values each type requires.
No error handling guidance. Tools do not indicate which errors are retryable, user-fixable, or fatal. No recovery paths (e.g., 'If object not found, call get_document_info to list available objects').