Skip to main content
Glama
rokibul-mist

rhino-mcp

by rokibul-mist
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Hybrid

rhino_export

Export all geometry from the Rhino model to a file. Specify a filename with extension or set export_type to choose the output format, such as STL.

Instructions

    Select all geometry and export to a file.
    
    The export format is inferred from the file extension; ``export_type``
    is used as the extension if ``file_name`` has none.
    
    Args:
    controller: RhinoController instance.
    file_name: Output filename (e.g. 'model.stl') or full path.
    folder: Optional folder override.
    export_type: File extension / format if not included in file_name
    (default 'stl').
    
    Returns:
    Dict with command result.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
folderNo
file_nameYes
export_typeNostl

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral disclosure burden. It does disclose a notable side effect (selecting all geometry before export) and mentions the return type, but it does not cover overwrite behavior, folder creation, or whether the selection state is preserved.

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 docstring is structured, front-loaded with the main action, and reasonably compact. The 'controller' argument line is slightly extraneous because it does not appear in the input schema, but it does not harm readability.

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?

The description covers the core export mechanism, parameters, and return value, but omits important file-handling details like overwrite behavior, folder creation, and whether the file path is resolved relative to the Rhino document. It also does not mention how to choose between this generic exporter and the format-specific siblings.

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

Parameters5/5

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

Schema description coverage is 0%, yet the description explains every schema parameter: file_name with an example, folder as an optional override, and export_type with a default and fallback behavior. This fully compensates for the bare input schema.

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 a specific action ('Select all geometry and export to a file') and clarifies that the format is inferred from the file extension. This makes the tool's purpose clear, though it does not explicitly distinguish it from format-specific siblings like rhino_export_stl or rhino_export_obj.

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 explicit guidance on when to use this tool versus the many format-specific export tools, nor any exclusions or alternative routing. The format-inference rule is useful but is a mechanism detail, not 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