Skip to main content
Glama
Sign In
self-host-fusion360-mcp

self-host-fusion360-mcp

by mystify59
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

fusion_rectangular_pattern

Pattern a 3D body along any axis by specifying copy count and spacing. Creates linear repetitions in Fusion 360.

Instructions

Pattern a body in a line along axis x/y/z: count copies, spacing mm apart.

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": "<body>",
      "count": "<count>",
      "spacing": "<spacing>"
    },
    "name": "fusion_rectangular_pattern"
  }
}

Input Schema

NameRequiredDescriptionDefault
axisNox
bodyYes
countYes
spacingYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already indicate non-readOnly and non-idempotent behavior. The description adds specific behavioral context: it creates copies of a body along an axis. However, it doesn't mention potential side effects or output, which is acceptable for a creation tool. No contradiction with 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?

The description is a single, concise sentence that front-loads the purpose and key parameters. Every word earns its place, with no redundancy or unnecessary details.

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?

The tool is relatively simple (4 params, no output schema). The description covers the purpose, axes, and key parameters. It might benefit from mentioning that 'body' can be an integer or string, but that is in the schema. Overall, it provides sufficient context for an agent to use it 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?

Schema coverage is 0%, so the description bears full burden. It explains 'count' as number of copies, 'spacing' as mm apart, and axis as x/y/z. 'body' lacks additional context but is self-explanatory. The description adds significant meaning for most parameters, compensating well.

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 it patterns a body in a line along axes x/y/z, with specific parameters for count and spacing. It effectively distinguishes itself from sibling tools like fusion_circular_pattern by specifying 'in a line'.

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?

The description implies usage for linear patterns and axes. While it doesn't explicitly state when not to use or mention alternatives, the context of sibling tools (especially fusion_circular_pattern) provides clear differentiation. Lacks explicit exclusion but is adequate.

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