Skip to main content
Glama
rokibul-mist

rhino-mcp

by rokibul-mist
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Hybrid

rhino_attractor_displace_points

Displace Rhino points toward or away from an attractor point or curve using a linear, inverse, or gaussian falloff, returning new points for form-finding.

Instructions

Displace each input point along the vector to an attractor with a falloff.

    Positive ``strength`` pulls toward the attractor; negative pushes
    away. The attractor is either a fixed point (``attractor_point``)
    or a curve (``attractor_curve_id``); for curves each point's
    attractor is the closest sample on the curve.

    Returns the *new* point IDs (the originals are deleted; this is a
    form-finding move, not a duplicating one).

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

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

The description explicitly discloses the destructive side effect: 'the originals are deleted; this is a form-finding move, not a duplicating one.' Annotations only carry readOnlyHint=false, so this deletion warning and the promise of new IDs add essential behavioral context beyond the structured data.

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 tightly structured: a clear first-sentence overview, then parameter behavior, then return/destructive consequence. Every sentence earns its place and there is no filler or repetition of schema noise.

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 mutating deformation tool, the description covers operation, attractor modes, strength direction, return value, and the critical deletion side effect. Combined with the schema's documentation of doc_id, falloff, max_distance, and point filtering, the agent has enough context to invoke the tool correctly.

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 description adds meaningful parameter relationships: positive strength pulls and negative pushes, the attractor can be a point or curve, and curves use the closest sample on the curve. It also clarifies that the returned IDs are new objects. The schema already documents falloff, max_distance, and doc_id, so the description compensates well for the key semantic gaps.

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 names a specific verb and resource: 'Displace each input point along the vector to an attractor with a falloff.' It clearly distinguishes this as an attractor-based point-deformation operation, unlike the many sibling move/soft-edit/bend/twist tools.

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?

The description implies use for attractor-driven form-finding and warns that it is 'not a duplicating one,' but it does not explicitly name alternative tools or state when to prefer this over sibling deformation operations. Context is conveyed through the operation's semantics rather than direct routing guidance.

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