Skip to main content
Glama

rhino_bim_metadata_set

Assign IFC entity types and property-set metadata to Rhino objects, enabling structured data export to IFC files.

Instructions

Tag objects with IFC entity + property-set metadata.

    Standalone writes ``Pset_RhinoMcp::<key>`` user_text on each object;
    bridge mode does the same and additionally pushes into Rhino's IFC
    property-set table so a subsequent IFC export carries them across.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
argsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Annotations indicate readOnlyHint=false, and the description confirms mutation by stating 'writes' and 'pushes'. It discloses two distinct modes (standalone vs. bridge) and their impact on IFC export, adding value beyond annotations. No contradictions.

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 extremely concise: three sentences, front-loaded with the core purpose, and no redundant information. Every sentence adds value.

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?

Given the existence of an output schema and detailed annotations, the description adequately covers behavioral context (two modes, IFC export). Minor omission: no mention of property optionality or object limits, but not critical.

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

Parameters1/5

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

The tool description contains no information about parameters beyond what is in the input schema. With schema description coverage at 0%, the description fails to compensate; it adds no additional meaning or usage hints for the complex 'args' parameter.

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 states 'Tag objects with IFC entity + property-set metadata' clearly specifying the verb, resource, and field scope. It distinguishes between standalone and bridge modes, differentiating from sibling tools like rhino_bim_pset_set and rhino_set_user_text.

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?

The description lacks explicit guidance on when to use this tool versus alternatives like rhino_bim_pset_set or rhino_set_user_text. No context on prerequisites, mode selection criteria, or comparison with siblings 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