Skip to main content
Glama
rokibul-mist

rhino-mcp

by rokibul-mist
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Hybrid

rhino_mesh_from_nurbs

Convert selected NURBS surfaces or polysurfaces to a mesh for rendering, with adjustable parameters for mesh density and quality.

Instructions

    Convert selected NURBS surfaces / polysurfaces to a render mesh.
    
    Args:
    controller: RhinoController instance.
    max_angle: Maximum angle between mesh normals (degrees).
    max_aspect: Maximum aspect ratio of mesh faces (0 = ignore).
    max_distance: Maximum distance from mesh edge to surface.
    max_edge: Maximum mesh edge length (0 = ignore).
    min_edge: Minimum mesh edge length.
    min_initial_grid: Minimum initial grid quads per surface.
    refine: Refine the mesh for better quality.
    jagged_seams: Allow jagged seams between surfaces.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
refineNo
max_edgeNo
min_edgeNo
max_angleNo
max_aspectNo
jagged_seamsNo
max_distanceNo
min_initial_gridNo

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 burden. It states that conversion happens but does not disclose whether new mesh objects are created, whether the original surfaces are modified or deleted, whether selection is required, or any side effects. The parameter list gives mesh settings but not operational behavior.

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 compact and well-structured: a single purpose sentence followed by a parameter list. Every line adds information, and the most important purpose statement is front-loaded. No filler or redundant restatement of the tool name.

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?

The parameter semantics are complete and an output schema exists, so return values do not need explanation. However, the description omits behavioral effects, prerequisites beyond 'selected', and guidance on choosing this over similar mesh-creation tools. For a conversion operation with no annotations, this is a notable gap.

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?

Although the schema has no descriptions, the description's Args block provides meaningful explanations for every schema parameter, including units ('degrees'), interpretation of zero values ('0 = ignore'), and specific roles like 'Minimum initial grid quads per surface'. This adds substantial value beyond the bare property names and defaults.

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 a specific action ('Convert'), resource ('selected NURBS surfaces / polysurfaces'), and result ('render mesh'). However, it does not explicitly distinguish itself from closely related siblings like rhino_mesh_from_surface or rhino_mesh_from_brep, which overlap in function.

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?

The phrase 'Convert selected NURBS surfaces / polysurfaces' implies the tool is used when the current selection contains NURBS geometry and a mesh is desired. There is no explicit when-to-use guidance, no mention of alternatives, and no clarification about which sibling to prefer.

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