Skip to main content
Glama
rokibul-mist

rhino-mcp

by rokibul-mist
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Hybrid

rhino_volume_centroid

Calculate the volume centroid of selected closed solids in Rhino, returning the centroid coordinates. Use this to precisely determine the center of mass for solid objects in your model.

Instructions

    Calculate the volume centroid of selected closed solids.
    
    Args:
    controller: RhinoController instance.
    
    Returns:
    Dict with command result containing centroid coordinates.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

The verb 'calculate' suggests a read-only operation and the return type is noted, but there is no explicit statement about side effects, selection changes, or behavior on invalid or inadequate selections. With no annotations, this is only partially transparent.

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 only two sentences and front-loads the main purpose, followed by the return information. It contains no fluff or unnecessary detail.

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 simple read-only centroid query, the description covers what is computed and what is returned. It does not specify behavior for missing selections or invalid closed solids, but the output schema likely fills the remaining detail.

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?

There are no schema parameters to document, so the high schema coverage means little additional explanation is required. The mention of the controller argument is minimal but consistent with the tooling pattern.

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 clearly identifies the action (calculate), the object (volume centroid), and the target (selected closed solids). It is distinct from related tools such as rhino_area_centroid and rhino_volume.

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 does not state when to use this tool instead of alternatives or mention any preconditions beyond having selected closed solids. It leaves the usage context 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