Skip to main content
Glama
rokibul-mist

rhino-mcp

by rokibul-mist
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Hybrid

rhino_set_render_resolution

Set the render output resolution for the active Rhino document by specifying width and height in pixels, ensuring the final image matches the required dimensions.

Instructions

    Set the document render output resolution.
    
    Args:
    width: Render width in pixels.
    height: Render height in pixels.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
widthNo
heightNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the action—setting document render output resolution—without explaining persistence, side effects, or whether it affects already-generated output. It does not contradict any annotations, but lacks meaningful behavioral depth.

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 main purpose is front-loaded in the first sentence, followed by a compact two-line parameter list. Each parameter line adds the useful 'in pixels' semantic, and there is no fluff.

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 two-parameter setter, the description is adequately sized but lacks workflow context: it does not mention whether this is a pre-render step, whether it persists across sessions, or how it interacts with other render settings. The output schema may clarify return values, but behavioral context remains absent.

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

Parameters3/5

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

With 0% schema description coverage, the description must compensate. It does add 'Render width in pixels' and 'Render height in pixels,' clarifying units, but it does not provide ranges, constraints, or parameter coupling, which would be valuable for a render configuration tool.

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 states 'Set the document render output resolution,' giving a specific verb and resource. It clearly identifies the tool's role among render-related siblings such as rhino_render_preview and rhino_render_to_file, though it does not explicitly name them to differentiate.

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 guidance on when to use this tool versus alternatives like rhino_render_setup, rhino_render_viewport, or rhino_render_to_file. It does not provide sequence hints, prerequisites, or exclusions, leaving the agent to infer the workflow.

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