Renders the active viewport to an image file at a specified output path, producing a static snapshot of the current model for documentation or review.
Render the active viewport to an image file (bridge required).
| Name | Required | Description | Default |
|---|---|---|---|
| args | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotation readOnlyHint=false is consistent with a write operation that produces a file. Beyond annotations, the description adds 'bridge required' and scopes the operation to the active viewport, which is useful. However, it does not disclose potential blocking behavior, file overwrite semantics, or failure conditions when no bridge is connected.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence with no filler. Every word contributes meaning, and the critical 'bridge required' caveat is included without bloating the text.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with overlapping siblings and four parameters, this description is too thin. The output schema may cover return values, but the description does not provide enough context about prerequisites, alternative tool selection, or parameter behavior to let an agent confidently invoke it in the right situation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description carries the burden of explaining parameters, but it only implies output_path and 'active viewport.' It does not clarify width, height, or doc_id beyond what the schema already provides via defaults and constraints.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb ('Render'), the resource ('active viewport'), and the outcome ('to an image file'). It is specific enough to identify the tool's core function, though it does not explicitly distinguish it from overlapping siblings like rhino_render_to_file or rhino_render_preview.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is given on when to choose this tool over closely related alternatives such as rhino_render_preview, rhino_render_to_file, or rhino_screenshot. The parenthetical 'bridge required' is a dependency note, not usage direction. An agent has to infer selection criteria from the name alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.