Skip to main content
Glama
rokibul-mist

rhino-mcp

by rokibul-mist
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Hybrid

rhino_align

Align selected objects in a specified direction—Left, Right, Top, Bottom, Vertical, Horizontal, Center, or Middle—to organize geometry precisely.

Instructions

    Align selected objects in a given direction.
    
    Valid directions: Left, Right, Top, Bottom, Vertical, Horizontal,
    Center, Middle.
    
    Args:
    controller: RhinoController instance.
    direction: Alignment direction keyword.
    
    Returns:
    Dict with command result.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
directionNoLeft

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It mentions inputs and a return dict but does not state that the tool modifies object positions, what happens with no selection, whether the operation is reversible, or any other behavioral side effects.

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 description is concise and well-structured: the purpose is front-loaded, the valid directions are clearly listed, and the Args/Returns sections are compact. No filler or redundant prose is present.

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 tool with an output schema, the description covers the direction values and general operation. It is minimally adequate, but missing details about the selection prerequisite, the exact alignment behavior for each direction, and error handling leave it incomplete for confident autonomous use.

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 compensates for the schema's 0% coverage by listing the valid direction keywords and indicating the direction parameter's purpose. However, it also mentions a 'controller' argument that is not present in the input schema, creating potential confusion about the actual callable interface.

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 and resource ('Align selected objects') and enumerates the valid alignment directions. It clearly communicates what the tool does, though it does not explicitly differentiate it from sibling tools like rhino_align_mesh_vertices.

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?

No guidance is provided on when to use this tool versus alternatives such as rhino_move, rhino_distribute, rhino_orient, or rhino_align_mesh_vertices. The only implied usage is that it operates on selected objects, but no explicit context or exclusions are given.

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