Skip to main content
Glama
rokibul-mist

rhino-mcp

by rokibul-mist
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Hybrid

gh_template_list

Read-only

Lists bundled Grasshopper templates and their parameter contracts, indicating when binaries are missing so users know which templates are ready to load.

Instructions

List bundled Grasshopper templates with their parameter contracts.

    ``available=False`` means the .gh binary has not been shipped yet —
    the contract is described in the manifest but loading it will fail
    until the binary is placed alongside the manifest.

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/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description adds meaningful behavioral context by defining the available=False state and explaining that loading will fail until the .gh binary is shipped. This helps the agent interpret list results without attempting doomed loads.

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 short, front-loaded with the core purpose, and every sentence adds value. The available=False caveat earns its place by preventing incorrect assumptions about template readiness.

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?

With an output schema present and a readOnly annotation, the description covers the key behavioral nuance that could cause failures. It is slightly incomplete only because it does not mention the relationship to load/run template tools, but this is a minor gap for a simple listing operation.

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 has only an empty args wrapper with no meaningful properties, so there are effectively no parameters to document. The description does not need to add parameter details; the baseline for an effectively zero-parameter tool is appropriate.

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 a specific verb and resource: 'List bundled Grasshopper templates with their parameter contracts.' This clearly identifies what the tool does and distinguishes it from generic listing tools like gh_component_list or gh_plugin_list by focusing on templates and their parameter contracts.

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 gives no guidance on when to use this tool versus alternatives such as gh_load_template or gh_run_template. There is no mention of prerequisites, exclusions, or a recommended workflow for discovering templates before loading them.

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