Skip to main content
Glama
rokibul-mist

rhino-mcp

by rokibul-mist
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Hybrid

rhino_set_grid

Adjust the Rhino viewport grid by setting snap spacing and the number of minor and major gridlines to match your modeling precision needs.

Instructions

    Configure viewport grid settings.
    
    Args:
    controller: RhinoController instance.
    grid_snap: Snap spacing size (default 1.0).
    minor_gridlines: Number of minor grid lines (default 10).
    major_gridlines: Number of major grid lines per minor (default 10).
    
    Returns:
    Dict with command result.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
grid_snapNo
major_gridlinesNo
minor_gridlinesNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, but it only discloses that the tool 'configures' settings (implying mutation) and returns a result dict. It omits whether changes persist, which viewport is affected, and what happens to grid settings not specified. The docstring also lists a 'controller' argument that the input schema does not accept, an inconsistency that could mislead an agent.

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 summary line is front-loaded and the Args/Returns structure is scannable. However, the 'controller: RhinoController instance' line is wasted space for a parameter the schema does not accept, and the Returns line adds little since an output schema already exists.

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 config tool with zero required parameters and an output schema, the description covers purpose, all parameter meanings, and return type. It leaves real gaps, however: it doesn't say which viewport is configured, whether omitted settings persist or reset, or how this relates to grid visibility and snap siblings. The phantom controller parameter further undermines completeness.

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?

Schema coverage is 0%, and the description compensates fully by giving each of the three schema parameters semantic meaning: snap spacing size, number of minor lines, and number of major lines per minor. The 'per minor' clarification is especially valuable since the schema only provides names and types. Minor deductions for documenting a phantom 'controller' parameter and quoting a default (1.0) that differs from the schema default (1).

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 line 'Configure viewport grid settings' states a specific verb and resource, making the core action clear. It doesn't, however, differentiate from grid-related siblings like rhino_toggle_grid (grid visibility) or rhino_set_snap (snap behavior), so an agent must infer the boundary between configuring grid metrics and toggling grids.

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 offers no guidance about when to use this tool versus alternatives. There is no mention of rhino_toggle_grid for showing/hiding the grid or rhino_set_snap for snap controls, nor any conditions or prerequisites such as an open document or active viewport.

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