Skip to main content
Glama
rokibul-mist

rhino-mcp

by rokibul-mist
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Hybrid

rhino_cmd_array_linear

Create a rectangular/linear array from selected objects by setting the number of items and spacing along X, Y, and Z axes.

Instructions

    Create a rectangular/linear array of selected objects.
    
    Args:
    controller: RhinoController instance.
    count_x: Number of items in X direction.
    count_y: Number of items in Y direction.
    count_z: Number of items in Z direction.
    spacing_x: Spacing between items in X.
    spacing_y: Spacing between items in Y.
    spacing_z: Spacing between items in Z.
    
    Returns:
    Dict with command result.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
count_xNo
count_yNo
count_zNo
spacing_xNo
spacing_yNo
spacing_zNo

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 behavior disclosure. It only says it creates an array and returns a command result; it does not mention document mutation, selection prerequisites, no-selection failure behavior, or coordinate/unit context. This is thin for an operation that modifies the Rhino document.

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 compact and front-loaded with a one-sentence purpose, followed by a clear parameter list. The main waste is the extraneous controller argument line, and the return description is vague ('Dict with command result'), but overall the structure is easy to scan.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

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

For a no-annotation tool with six parameters and many closely related sibling tools, the description is incomplete. It does not state the selection precondition, how spacing relates to the current document units, or how this tool differs from rhino_array_linear and rhino_array_rectangular. The presence of an output schema reduces the need to document return values, but the operational context remains under-specified.

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 0% description coverage, and the description does add meaning to all six schema parameters by explaining counts and spacings. However, it also documents a 'controller: RhinoController instance' argument that is absent from the input schema, which could confuse an agent. It also omits units and constraints for spacing values.

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 creates a rectangular/linear array of selected objects, with a specific verb and resource. However, the phrase 'rectangular/linear array' conflates two related concepts, and the tool name rhino_cmd_array_linear sits alongside rhino_array_linear and rhino_array_rectangular without explaining how it differs.

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 provides no guidance on when to use this tool versus the many sibling array tools such as rhino_array_linear, rhino_array_rectangular, rhino_array_polar, or rhino_cmd_array_polar. It also does not explicitly instruct the user to select objects first, despite saying 'selected objects' as a requirement.

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