Skip to main content
Glama

rhino_export_draco

Compresses Rhino mesh objects into a Google Draco .drc file for smaller mesh storage or transfer; export selected meshes or every mesh in the document.

Instructions

Compress mesh objects to a Google Draco .drc file (standalone, rhino3dm).

    Exports one mesh by id, a list of meshes, or every mesh in the
    document; several meshes are merged into one Draco mesh. Non-mesh
    objects are skipped (rhino3dm cannot tessellate Breps).
    

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "args": "<args>"
    },
    "name": "rhino_export_draco"
  }
}

Input Schema

NameRequiredDescriptionDefault
argsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations provide only readOnlyHint=false, so the description carries most of the burden. It does disclose two important behaviors: multiple meshes are merged into one Draco mesh, and non-mesh objects are silently skipped rather than erroring. It says nothing about whether the target file or directory is created/overwritten, nor about failure modes on bad ids, which matters for a write-to-disk export.

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?

Three tight sentences, front-loaded with the output format and followed by input scoping and the skipping caveat. No filler, though the parenthetical about rhino3dm not tessellating Breps repeats the surrounding sentence's point.

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?

An output schema exists, so return values need not be explained. For an eight-parameter export tool that writes to disk, the description covers input selection and the merge/skip behavior but omits file-overwrite behavior and the meaning of the several encoding options, leaving it adequate rather than complete.

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 reported as 0%, so the description should compensate. It does add meaning for object_ids (one id, a list, or all meshes, with merging semantics), but it leaves include_normals, include_vertex_colors, include_texture_coordinates and the quantization/compression knobs entirely unexplained, which is half the parameter surface.

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 gives a specific verb and resource ('Compress mesh objects to a Google Draco .drc file') and clarifies it is standalone rhino3dm output, which distinguishes it from the format siblings like rhino_export_obj or rhino_export_stl without naming them.

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?

It explains the accepted input scope (one id, a list, or all meshes) and warns that non-mesh objects are skipped because Breps cannot be tessellated, which is genuinely useful selection context. However, it never states when an agent should choose this format over another export sibling, so usage is only implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools