Skip to main content
Glama

rhino_subd_inspect

Read-only

Inspect Rhino SubD control nets to report topology counts, vertex/edge tags, boundaries, creases, sharp edges, corners, and face side-count distribution.

Instructions

Report SubD topology: vertex/edge/face counts, vertex and edge tags, boundary / crease / sharp edges, corners, and face side-count histogram.

    Standalone reads the SubD control net through rhino3dm 8.32+ iterators.
    

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "args": "<args>"
    },
    "name": "rhino_subd_inspect"
  }
}

Input Schema

NameRequiredDescriptionDefault
argsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.0

TDQS

A4/5.0
Behavior3/5

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

The readOnlyHint=true annotation already carries the safety profile, so the description only needs to add context. It does add that the tool reads the SubD control net through rhino3dm 8.32+ iterators, which implies an out-of-process/version-gated read path, but it never clarifies whether Rhino must be running, how validation works, or that listings may be truncated by the limit parameter.

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?

Two short sentences with no filler: the enumeration of returned metrics is front-loaded and the implementation note follows. Every clause carries information an agent could use; nothing is redundant with the name or title.

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?

For a low-complexity, read-only inspection tool with an output schema and fully annotated safety hints, the description covers what is counted and how it is read. The remaining gap is operational: it never states edge cases such as a non-SubD object_id or that limit caps the crease/corner output, though the schema mitigates the latter.

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?

The schema documents every parameter inline (object_id GUID, doc_id handle, limit cap on crease/corner listings, include_creases toggle), so parameter semantics are largely handled by structured data and the description need not repeat them. The description adds only marginal framing ('report topology' tells the agent why include_creases matters) and does not warn about limit-based truncation, so it is solid but not additive.

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 ('Report SubD topology') and then enumerates exactly what is reported: vertex/edge/face counts, tags, boundary/crease/sharp edges, corners, and a face side-count histogram. That specificity makes it clearly distinguishable from siblings like rhino_create_subd (mutation) and rhino_subd_to_nurbs (conversion), since this one only reads topology.

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?

Usage is only implied: an agent can infer 'call this to inspect a SubD's topology,' and the second sentence hints at a standalone read path via rhino3dm iterators. There is no explicit when-to-use/when-not guidance, no mention of what happens with a non-SubD object_id, and no statement of prerequisites (e.g., whether a live document is required).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools