Skip to main content
Glama
rokibul-mist

rhino-mcp

by rokibul-mist
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Hybrid

rhino_purge

Purge unused layers, blocks, and materials to reduce Rhino file size and clean up the model. Delete unreferenced document objects for a streamlined file.

Instructions

    Purge unused document objects to reduce file size.
    
    Args:
    controller: RhinoController instance.
    purge_unused_layers: Remove layers with no geometry (default True).
    purge_unused_blocks: Remove unreferenced block definitions (default True).
    purge_unused_materials: Remove unreferenced materials (default True).
    
    Returns:
    Dict with command result.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
purge_unused_blocksNo
purge_unused_layersNo
purge_unused_materialsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It does disclose that it removes layers with no geometry, unreferenced block definitions, and unreferenced materials, which signals destructive cleanup. However, it does not explicitly warn that purging is permanent or potentially irreversible for user-created definitions that happen to be unreferenced.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The one-sentence summary is front-loaded and the parameter list is compact. However, it repeats default values already present in the schema, includes the extraneous controller argument, and the Returns line duplicates what the output schema already communicates.

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 destructive purge operation with no annotations, the description should explicitly mention permanence and warn that unreferenced content will be removed. It also lacks any pointer to the layer-only alternative. It covers the core parameters and purpose, but not the full safety context needed for confident invocation.

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

Parameters4/5

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

Schema description coverage is 0%, but the description compensates by explaining each boolean parameter in plain language and clarifying what 'unused' means for each category. It loses some credit because it also lists a 'controller' argument that is not present in the input schema, which could confuse the agent.

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 names a concrete operation: purge unused document objects to reduce file size, and enumerates the affected categories (layers, blocks, materials). This is clear and specific, but it does not distinguish itself from sibling rhino_layer_purge_unused, which could be redundant for layer-only purging.

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 gives one clear use context: reducing file size by removing unused document objects. However, it does not say when to prefer this tool over rhino_layer_purge_unused or object deletion, and it provides no prerequisites or when-not-to-use 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