Skip to main content
Glama

rectangular_pattern

Create a rectangular pattern of selected bodies along one or two directions, specifying spacing and instance count.

Instructions

Create a rectangular pattern of bodies along one or two directions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
body_namesYesArray of body names to pattern.
direction1_axisYesFirst direction axis: 'X', 'Y', or 'Z'.
count1YesNumber of instances in direction 1.
spacing1YesSpacing in direction 1 in mm.
direction2_axisNoSecond direction axis (optional).
count2NoNumber of instances in direction 2.
spacing2NoSpacing in direction 2 in mm.
Behavior2/5

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

No annotations are provided, and the description does not disclose side effects (e.g., whether original bodies are modified or preserved), required permissions, or any destructive behavior. For a tool creating patterns, more transparency is needed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence that is concise and to the point. It avoids redundancy but could be slightly more informative without becoming verbose.

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

Completeness3/5

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

Given the moderate complexity (7 parameters, no output schema), the description provides the basic purpose but lacks context on how the pattern is applied (e.g., bodies are selected by name) and does not explain return behavior.

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 provides full descriptions for all 7 parameters (100% coverage). The description adds no extra semantics beyond stating the overall functionality, so it meets the baseline but does not enhance understanding.

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 clearly states the tool creates a rectangular pattern of bodies along one or two directions. It distinguishes from siblings like 'circular_pattern' and 'mirror' through the specific term 'rectangular pattern.'

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?

No guidance on when to use this tool versus alternatives such as 'circular_pattern' or 'mirror'. The description does not mention any context or restrictions for usage.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mikan-atomoki/text-to-model'

If you have feedback or need assistance with the MCP directory API, please join our Discord server