Skip to main content
Glama
rokibul-mist

rhino-mcp

by rokibul-mist
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Hybrid

gh_components_search

Read-onlyIdempotent

Find the GUID of any Grasshopper component by searching the catalog. Filter by plugin or category to identify the right component before adding it to the canvas.

Instructions

Search the Grasshopper component catalog (built-in + plugin-supplied).

    Returns ``rows`` of ``{guid, name, nickname, category, subcategory,
    description, plugin}`` and a ``summary`` block with match counts.
    Use this to find the GUID needed by ``gh_add_component`` before
    dropping a component on the canvas.

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 mark readOnlyHint and idempotentHint; the description aligns and adds detail about return shape (rows fields, summary block) and catalog scope. No mention of pagination or exact match semantics, but the safety profile is covered by annotations.

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?

Three short sentences, no redundancy, front-loaded with verb and resource. Efficient.

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 read-only search tool with a rich parameter schema and output format described, the description is sufficient; the workflow hint to gh_add_component completes the picture.

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 nested schema fully describes limit, query, plugin, and category, so the description doesn't need to repeat them. It adds only the workflow tie to gh_add_component. While the reported coverage is 0% at the top level, the visible schema provides complete parameter documentation; description doesn't add further meaning, so baseline 3.

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 identifies the verb 'Search', the resource 'Grasshopper component catalog', and scopes it as 'built-in + plugin-supplied'. It names the sibling gh_add_component and clarifies the catalog’s purpose, distinguishing it from sibling tools like gh_component_list and gh_plugin_list.

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?

Explicitly states the intended workflow: use to find the GUID needed by gh_add_component before dropping a component. It lacks exclusion criteria or alternative routing, but the use case is unambiguous.

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