Skip to main content
Glama
rokibul-mist

rhino-mcp

by rokibul-mist
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Hybrid

rhino_bim_pset_get

Read-onlyIdempotent

Retrieve BIM PropertySet data from a Rhino object, returning properties grouped by set name. Optionally filter results to a specific property set.

Instructions

Read PropertySet entries off an object.

    Bridge mode reads from the live RhinoCommon UserString table; standalone
    mode reads from rhino3dm UserStrings on the saved 3dm document. The
    result groups properties by PropertySet name (``psets`` field).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
argsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds valuable behavioral detail: the mode-dependent data source difference and the result grouping by PropertySet name in a 'psets' field.

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 concise and front-loaded with the core purpose, followed by mode behavior and result grouping. Every sentence earns its place without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read tool with only one required parameter, output schema present, and annotations covering idempotence and read-only behavior, the description is complete. It explains mode differences and result structure sufficiently.

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 input schema already documents object_id, doc_id, and pset_name with descriptions and defaults, so the description does not need to repeat parameter details. It adds only the grouping context, not additional parameter semantics.

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 opens with a specific verb and resource: 'Read PropertySet entries off an object.' This clearly identifies the tool's function and differentiates it from sibling tools like rhino_bim_pset_set and rhino_bim_pset_delete.

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 provides clear context by explaining bridge mode versus standalone mode and which data source each reads. It does not explicitly compare against alternatives such as rhino_bim_pset_set, but the read-only nature and mode guidance are sufficient for an agent to understand when to use it.

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