Skip to main content
Glama
rokibul-mist

rhino-mcp

by rokibul-mist
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Hybrid

rhino_insert_block

Insert a named block into the Rhino document at the specified X, Y, Z coordinates, with optional uniform scale and rotation angle. Set the block definition name and placement parameters.

Instructions

    Insert a block instance into the document.
    
    Args:
    name: Block definition name to insert.
    x, y, z: Insertion point.
    scale: Uniform scale factor.
    rotation: Rotation angle in degrees.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xNo
yNo
zNo
nameYes
scaleNo
rotationNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

Annotations are absent, so the description carries the full burden. It identifies the operation as an insertion (a mutating action) but does not disclose what happens when 'name' references a nonexistent block definition, whether the instance lands on the current layer, or unit expectations for x/y/z. The behavior disclosed is essentially the action already implied by the tool name.

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?

Roughly 40 words: a one-sentence action summary followed by a compact Args list. Front-loaded with the operation, no filler, and every parameter line adds value given the empty schema descriptions.

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?

Given the output schema exists, return values need no explanation, and parameter semantics are well covered. But with six parameters and no annotations, an agent still lacks context on prerequisites (definition must exist), error behavior, and when this tool is preferred over block_define/block_explode. Adequate but with clear gaps.

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%, and the description compensates by explaining all six parameters. It adds real meaning: 'rotation ... in degrees' (preventing a radian assumption), 'Uniform scale factor,' and 'Block definition name' clarifying that name refers to an existing definition. This goes beyond the bare 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?

States 'Insert a block instance into the document' — a specific verb and resource that is immediately distinguishable from siblings like rhino_block_define, rhino_block_list, and rhino_block_explode. The description clearly communicates the operation without requiring schema inspection, though it doesn't explicitly name any sibling.

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?

No guidance on when to use this tool versus rhino_block_define (which creates the definition this tool references), rhino_block_explode, or other block tools. No prerequisite stated (e.g., the block definition must exist before insertion), and no mention of alternatives or exclusions. An agent must infer when this is appropriate.

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