Skip to main content
Glama
rokibul-mist

rhino-mcp

by rokibul-mist
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Hybrid

rhino_status

Check Rhino connection status and locate the default files directory. Get current status and directory path for Rhino operations.

Instructions

    Return the current Rhino connection status plus the default files directory.
    
    Args:
    controller: RhinoController instance.
    
    Returns:
    Dict containing status info and rhino_files_dir.

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

C2.9/5.0
Behavior3/5

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

There are no annotations, so the description carries the behavioral transparency burden. It indicates a read-only operation through 'Return' and states the output contents, but it does not disclose what happens if the connection is unavailable, whether it establishes a connection, or any error behavior. Some transparency is present, but gaps remain.

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 description is short and front-loaded with the main purpose. However, the Args line is unnecessary and inconsistent with the empty schema, and the Returns line partially repeats the first sentence's mention of the default files directory. Not every sentence fully earns its place.

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 zero-parameter status tool with an output schema, the description is mostly adequate. Missing elements include connection prerequisites, possible status values, and behavior when Rhino is not connected. The phantom controller argument also adds ambiguity that a more complete description would avoid.

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

Parameters2/5

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

The input schema has zero parameters, so parameter documentation is unnecessary. However, the description includes 'Args: controller: RhinoController instance,' which introduces a parameter absent from the schema. This is misleading and could cause an agent to attempt passing an argument that the schema does not accept.

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 the tool returns the current Rhino connection status and the default files directory, which is a specific verb + resource. It does not explicitly distinguish itself from sibling tools like rhino_system_info, but the resource and scope are specific enough to avoid major confusion.

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 gives no explicit guidance about when to use this tool versus alternatives, no prerequisites, and no exclusions. The purpose implies it is for checking connection status, but that is not stated as actionable usage guidance.

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