Skip to main content
Glama

rhino_batch_modify

Modify many Rhino objects at once: apply transformations, color, layer, visibility, and name changes in a single call, all wrapped in one undo record. Optionally apply the same modifications to all objects.

Instructions

Modify many objects in a single call.

    Each spec can include any combination of: translation, rotation,
    scale, colour, layer, visibility, and name.  All changes are wrapped
    in one undo record — ``rhino_undo(steps=1)`` reverts the entire batch.

    When ``apply_to_all`` is ``True``, the modifications from the first
    spec are applied to every object in the document.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
argsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

The description discloses that changes are wrapped in one undo record and explains apply_to_all behavior. However, it does not mention that modifications are destructive, what happens to unmodified properties, or any permissions/performance considerations. Annotations provide no additional behavioral hints.

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 three concise sentences, front-loading the main purpose and key behavior. No unnecessary words, and each sentence adds value: purpose, undo feature, apply_to_all special case.

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?

The description covers the essential aspects: batch operation, modifiable properties, undo behavior, and apply_to_all mode. It does not explain return value, but an output schema exists. Missing details like error handling or maximum objects (implied by schema maxItems) are not critical. Fairly complete for a batch 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?

The description lists the fields that can be modified in each spec (translation, rotation, etc.) and explains the apply_to_all flag. However, with schema description coverage at 0%, the description does not delve into the semantics of each parameter (e.g., coordinate units, scaling bounds). The schema itself contains descriptions, but the coverage metric suggests they are not counted.

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 it modifies many objects in a single call, lists the modifiable properties (translation, rotation, scale, colour, layer, visibility, name), and distinguishes from single-object modification tools by emphasizing batch operation and undo encapsulation.

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

Usage Guidelines4/5

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

The description implies use for multiple objects and explains the apply_to_all mode, but does not explicitly state when to prefer this tool over single-object alternatives like rhino_move or rhino_rotate. The context of siblings makes it clear, but no direct guidance is provided.

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