Skip to main content
Glama
rokibul-mist

rhino-mcp

by rokibul-mist
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Hybrid

rhino_set_snap

Set grid snap behavior in Rhino by toggling it on or off and adjusting snap size for accurate modeling.

Instructions

    Enable or disable grid snap and set snap spacing.
    
    Args:
    controller: RhinoController instance.
    enabled: True to enable snap, False to disable.
    snap_size: The snap grid size (default 1.0).
    
    Returns:
    Dict with command result.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
enabledNo
snap_sizeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It clearly discloses the state-changing behavior (enable/disable snap, set spacing) and mentions a returned command result. However, it does not explain side effects, persistence, or how snap_size interacts with the enabled flag, though for a simple configuration tool this is acceptable.

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 compact and front-loaded with the main purpose. The Args and Returns sections are minimal and contain no filler. Every sentence contributes useful information.

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

Completeness4/5

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

For a low-complexity settings tool with two optional parameters and an output schema, the description covers the essential invocation details: what it does, parameter meanings, defaults, and return type. It could be more complete with explicit usage guidance, but nothing critical is missing for basic correct invocation.

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 description coverage is 0%, so the description must compensate. It does: 'enabled' is explained as True/False toggles, and 'snap_size' is described as the snap grid size with a default of 1.0. The only minor issue is documenting a 'controller' argument that is absent from the input schema, which could cause slight confusion.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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: 'Enable or disable grid snap and set snap spacing.' This clearly distinguishes it from related sibling tools like rhino_set_osnap (object snap) and rhino_toggle_grid (grid visibility).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use the tool—when the user wants to control grid snap or its spacing—but it does not explicitly mention alternatives or state when not to use it. There is no comparison with rhino_set_osnap or rhino_set_grid, so the routing guidance is only implicit.

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