Skip to main content
Glama
rokibul-mist

rhino-mcp

by rokibul-mist
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Hybrid

rhino_cmd_distance

Measure distance between two points in Rhino. Provide coordinates as x,y,z strings or run interactively to get the result.

Instructions

    Measure the distance between two points.
    
    If pt1/pt2 are provided they should be formatted as "x,y,z" strings.
    Otherwise the command runs interactively.
    
    Args:
    controller: RhinoController instance.
    pt1: Optional first point as "x,y,z".
    pt2: Optional second point as "x,y,z".
    
    Returns:
    Dict with command result.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pt1No
pt2No

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are present, so the description must self-disclose effects. It does disclose the interactive fallback and describes the return value as a dict, which is useful. It does not explicitly state whether the operation is non-destructive or whether object selection is involved.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core content is compact and front-loaded. The later Args section is largely redundant with the earlier paragraph and adds a controller argument that does not appear in the input schema.

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?

For a simple two-parameter measurement command, the description covers coordinate formats and the interactive behavior, and an output schema exists for return values. However, the absence of annotation safety context, the undocumented controller mention, and no differentiation from rhino_distance leave minor gaps.

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?

The input schema provides no descriptions for pt1 or pt2, and coverage is 0%. The description adds the 'x,y,z' string format and marks both parameters as optional, which meaningfully compensates for the schema gap. It does not explain coordinate units or the undocumented controller argument.

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 opening sentence states a specific verb and resource: measure the distance between two points. However, it does not differentiate this tool from the sibling rhino_distance, which has the same apparent purpose.

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 explains how to provide points and warns that omitting them runs interactively, but it gives no guidance on when to prefer this tool over alternatives such as rhino_distance. No exclusions or selection criteria are provided.

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