Skip to main content
Glama
rokibul-mist

rhino-mcp

by rokibul-mist
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Hybrid

rhino_edge_srf

Construct a surface by selecting 2, 3, or 4 bounding edge curves, enabling quick gap-filling and complex patch creation.

Instructions

    Build a surface from 2, 3, or 4 edge/curve inputs.
    
    Pre-select the bounding edges (2-4) before calling.
    
    Args:
    controller: RhinoController instance.
    num_edges:  Number of edge curves (2, 3, or 4).
    
    Returns:
    Dict with 'status' and 'command' keys.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
num_edgesNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/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 discloses the core behavior—building a surface—and the return shape, but it does not describe side effects, failure conditions, or what happens if the selection count does not match num_edges.

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 front-loaded: the purpose is stated immediately, followed by the essential precondition and then Args/Returns. There is no filler or redundant material.

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?

It covers the main prerequisite and return shape, but it misses the relationship between num_edges and the number of selected curves, and it includes a phantom controller argument. For a simple creation tool this is nearly sufficient, but the selection-count ambiguity leaves real room for incorrect invocation.

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

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds meaning to num_edges by explaining it as the number of edge curves and restricting it to 2, 3, or 4, which the bare schema lacks. However, it also lists a controller argument that is absent from the input schema, which could mislead an agent into passing an invalid parameter.

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 that the tool builds a surface from 2, 3, or 4 edge/curve inputs. It is specific about both the action and the resource, though it does not explicitly distinguish itself from surface-building siblings like rhino_network_surface or rhino_loft.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides a clear, actionable precondition: pre-select the bounding edges before calling. It does not, however, explain when to prefer this tool over alternative surface-creation tools or mention any exclusions.

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