Skip to main content
Glama
rokibul-mist

rhino-mcp

by rokibul-mist
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Hybrid

rhino_surface_developable_score

Read-only

Evaluate surface developability by sampling normal angles across a grid, returning a 0-1 score and deviation metrics to identify if a surface is flattenable without distortion.

Instructions

Estimate how far a surface deviates from being developable.

    Samples a (sample_u+1) x (sample_v+1) grid of normals; for each
    interior 2x2 block computes the maximum angle (in radians) between
    adjacent normals. Reports max / mean / RMS over the whole sheet
    plus a 0..1 normalised score (0 = perfectly developable,
    1 = π/2 normal swing within a single cell).

    A truly developable surface (cone, cylinder, plane) returns ~0;
    a sphere section returns a positive value proportional to the
    spanned solid angle.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
argsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, the description explains exactly how the measurement is computed: sampling a grid of normals, computing maximum angles in 2x2 blocks, and reporting max/mean/RMS plus a normalized score. It also gives concrete reference behavior for developable and non-developable surfaces.

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 purpose is front-loaded and every subsequent sentence adds value: algorithm, metric definitions, normalization, and reference examples. There is 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.

Completeness5/5

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

For a read-only analysis tool with an output schema and readOnlyHint annotation, the description is complete. It defines what is measured, how it is measured, what the outputs mean, and how to interpret scores. No critical operational facts are missing.

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

Parameters2/5

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

With schema description coverage reported as 0%, the description needed to explain the parameters, but it only indirectly references sample_u and sample_v via the grid formula. It does not explain surface_id, doc_id, defaults, or the effect of sample resolution, leaving the agent to infer parameter meaning from names and schema alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Estimate how far a surface deviates from being developable.' It then details the algorithm, output metrics, and expected values for example geometries, making the tool's role unmistakable among the many sibling analysis tools.

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 clearly conveys when to use the tool: whenever developability of a surface is in question. It also provides interpretable examples (developable surfaces return ~0, spheres return positive values). It does not explicitly name alternatives or state when not to use it, stopping short of a 5.

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