Skip to main content
Glama
rokibul-mist

rhino-mcp

by rokibul-mist
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Hybrid

rhino_quad_remesh

Convert selected objects into a uniform quad mesh by specifying the target quad count, adaptivity percentage, and hard-edge preservation for cleaner topology.

Instructions

    Remesh selected objects into a uniform quad mesh.
    
    Args:
    controller: RhinoController instance.
    target_quad_count: Target number of quad faces.
    adaptive_size: Adaptive size percentage (0–100).
    detect_hard_edges: Preserve hard edges during remeshing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
adaptive_sizeNo
detect_hard_edgesNo
target_quad_countNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3/5.0
Behavior2/5

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It says 'Remesh selected objects' but does not state whether the original geometry is modified in place, whether a new object is created, what happens if nothing is selected, or whether the operation is reversible. This is a meaningful gap for a mutation-type tool.

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 main action is front-loaded in one clear sentence, followed by a compact parameter list. No filler or redundant restatement of the tool name appears, although the 'Args' formatting is somewhat mechanical and could be tightened.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations and a large sibling toolset, the description lacks key contextual details: when to prefer this tool over quadrangulate/triangulate/rebuild mesh, whether selection is mandatory, and what happens to the original objects. The parameter documentation is adequate, but the operational context is incomplete for an agent to safely invoke this tool.

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

Parameters4/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 compensate. It provides concise meanings for all three schema parameters: target count, adaptive size percentage, and hard-edge preservation. The extra 'controller' arg is not in the schema, which is slightly confusing, but the provided parameter definitions add real value beyond the bare schema types 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 states a specific verb ('Remesh'), resource ('selected objects'), and outcome ('uniform quad mesh'), so an agent can tell this is a quad-mesh generation operation. However, it does not differentiate from the very similar sibling rhino_quadrangulate_mesh, which likely targets the same outcome.

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 implies that objects must be selected, but gives no explicit when-to-use guidance, no exclusions, and no alternatives. With several mesh-remeshing siblings available, an agent receives no help deciding between this tool and rhino_quadrangulate_mesh or rhino_triangulate_mesh.

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