Skip to main content
Glama
rokibul-mist

rhino-mcp

by rokibul-mist
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Hybrid

rhino_set_units

Set the current document's unit system to Millimeters, Meters, Inches, or other supported units to ensure accurate modeling and measurement in Rhino.

Instructions

    Set the document unit system.
    
    Args:
    controller: RhinoController instance.
    unit_system: One of Millimeters, Meters, Centimeters, Inches, Feet, etc.
    
    Returns:
    Dict with command result.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
unit_systemNoMillimeters

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are present, so the description carries the full behavioral disclosure burden. It only states that the tool sets the unit system and returns a dict; it does not mention side effects, whether the change persists, or whether it affects the active document.

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 short, front-loaded with the core purpose, and has no filler. Args and Returns sections are compact and add relevant information.

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 one-parameter setting tool, the description is adequate but incomplete. It lacks exact valid unit values, does not disambiguate from rhino_document_units_set, and provides no behavioral caveats. The output schema covers return value structure, but the overall context is minimally viable.

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 schema has zero description coverage, but the description compensates partially by enumerating example unit_system values: Millimeters, Meters, Centimeters, Inches, Feet. However, 'etc.' is vague, and the description mentions a 'controller' argument that is not present in the input schema.

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 the action ('Set the document unit system') with a specific verb and resource. However, it does not differentiate this tool from the sibling rhino_document_units_set, which appears to serve the same 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?

There is no guidance on when to use this tool instead of rhino_document_units_set or any other unit-related tool. No context, prerequisites, or exclusions 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