Skip to main content
Glama
rokibul-mist

rhino-mcp

by rokibul-mist
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Hybrid

rhino_cmd_twist

Apply a twist deformation to Rhino objects with an interactively picked axis and a specified angle. Solves the need to quickly twist geometry in Rhino.

Instructions

    Apply a twist deformation to selected objects.
    
    The twist axis is picked interactively.
    
    Args:
    controller: RhinoController instance.
    angle: Total twist angle in degrees.
    
    Returns:
    Dict with command result.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
angleNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior2/5

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

Discloses that the axis is picked interactively, but does not mention the effect on objects, undo behavior, or that it modifies the selection. Since there are no annotations, the description carries the full burden and is insufficient.

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?

Two short sentences with no extraneous words. It is efficient and to the point, but lacks the detail needed for a complete tool description.

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 tool with one parameter and an interactive step, it omits parameter explanation and expected outcome. The description is incomplete for an agent to use it confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The 'angle' parameter is not described at all. There is no mention that angle is the twist angle in degrees or any unit. With 0% schema coverage, the description adds no meaning to the parameter.

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?

Clearly states it applies a twist deformation to selected objects and mentions interactive axis picking. However, it does not differentiate from the similar-sounding rhino_twist among siblings, so slightly less clear on purpose differentiation.

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

Usage Guidelines1/5

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

No guidance on when to use this command versus other deformation or twist tools. It doesn't mention prerequisites, intended scenarios, or cases where alternative tools might be preferred.

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