Skip to main content
Glama

rhino_screenshot

Captures a viewport screenshot from Rhino, writes a PNG to a specified path, and optionally returns the image as base64 for AI analysis.

Instructions

Capture a viewport screenshot (bridge required).

    With ``as_base64=True`` the response includes ``image_base64`` so
    the LLM can inspect the render inline. The PNG is also written to
    ``path`` regardless, for the user to save/share.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
argsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

With minimal annotations (readOnlyHint=false), the description adds value by disclosing the inline base64 option and that the PNG is written to path. No contradictions found.

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 concise, two sentences with a clear structure. Every sentence adds value without fluff.

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?

Given the tool has an output schema (not shown), the description appropriately covers the key behavioral aspects (base64 and file output). Minor gap: no explanation of 'bridge' but acceptable for a screenshot tool.

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?

Schema description coverage is 0%, but the description indirectly references 'as_base64' and 'path'. However, the input schema already provides detailed parameter descriptions, so the baseline of 3 applies.

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 states the tool captures a viewport screenshot, with specific verb 'Capture' and resource 'viewport screenshot'. It distinguishes itself from sibling tools as the only screenshot-related tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description mentions 'bridge required' as a prerequisite but does not explicitly state when to use this tool versus alternatives or provide exclusions. Usage context is implied but not fully explicit.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/EaseHee/rhino-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server