Skip to main content
Glama
Sign In
Fusion360 MCP Server

Fusion360 MCP Server

by faust-machines
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Rectangular Pattern

rectangular_pattern

Create rectangular arrays of 3D bodies in Fusion 360 by specifying row and column counts with spacing parameters for CAD automation.

Instructions

Pattern a body in rows and columns

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": {
      "body_name": "<body_name>"
    },
    "name": "rectangular_pattern"
  }
}

Input Schema

NameRequiredDescriptionDefault
body_nameYes
x_countNo
x_spacingNoSpacing between columns (cm)
y_countNo
y_spacingNoSpacing between rows (cm)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations indicate this is a mutable (readOnlyHint=false), non-idempotent, non-destructive operation. The description adds that it patterns 'a body', implying it operates on existing geometry rather than creating new bodies from scratch. However, it lacks details on what 'pattern' entails (e.g., creates copies, maintains associations) or behavioral traits like error conditions or performance implications.

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?

Extremely concise with a single, front-loaded sentence: 'Pattern a body in rows and columns'. Every word contributes directly to the tool's purpose without any fluff or redundancy.

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?

For a 5-parameter mutation tool with no output schema and moderate schema coverage (40%), the description is minimal. It covers the core action but lacks details on inputs, outputs, error handling, or dependencies. Annotations help by clarifying mutability and safety, but more context would aid agent decision-making.

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?

Schema description coverage is 40% (only x_spacing and y_spacing have descriptions). The description mentions 'rows and columns', which aligns with y_count/rows and x_count/columns parameters, adding semantic context. However, it doesn't explain 'body_name' (the target) or default behaviors, leaving gaps despite partial compensation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('pattern') and resource ('a body'), specifying it's done 'in rows and columns'. It distinguishes from sibling 'circular_pattern' by implying rectangular vs. circular arrangement, but doesn't explicitly differentiate from other patterning or creation tools like 'mirror' or 'create_component'.

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 like 'circular_pattern', 'mirror', or array creation methods. It doesn't mention prerequisites (e.g., needing an existing body) or exclusions, leaving the agent to infer usage from context alone.

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