Skip to main content
Glama
rokibul-mist

rhino-mcp

by rokibul-mist
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Hybrid

rhino_sun_settings

Control Rhino's sun and sky by enabling/disabling sunlight and setting latitude, longitude, date, and hour for accurate daylight and shadow studies.

Instructions

    Configure the Rhino sun/sky system via Python.
    
    Args:
    enabled: Enable or disable the sun.
    latitude: Observer latitude in degrees.
    longitude: Observer longitude in degrees.
    year, month, day: Date settings.
    hour: Hour of day (24h float, e.g. 14.5 = 2:30 PM).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dayNo
hourNo
yearNo
monthNo
enabledNo
latitudeNo
longitudeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/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 lists parameters. It does not disclose persistence, document-level side effects, whether the sun/sky system is enabled by default, or how this affects rendering and solar analysis tools.

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?

The description is compact and front-loaded with the purpose, followed by a clear argument list. Minor filler includes 'via Python' and unnecessary leading whitespace.

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?

It covers all parameters and an output schema exists, so return-value documentation is not required. Still, it omits context about how sun settings interact with sun position, sun path, shadow projection, or render setup, leaving the agent to infer the tool's place in a larger workflow.

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, and it does by explaining all seven parameters: enabled, observer latitude/longitude in degrees, the date group, and hour with a concrete example. However, the hour example says '24h float' while the schema types it as integer, introducing a potential conflict.

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 starts with 'Configure the Rhino sun/sky system,' which identifies a specific resource and a clear action. It does not, however, distinguish itself from closely related sibling tools like rhino_sun_position or rhino_sun_path.

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?

There is no guidance on when to use this tool versus the many sun-, render-, or environment-related alternatives. The argument list does not provide selection criteria, prerequisites, or exclusions.

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