Skip to main content
Glama
tbrito88

Fusion360 Live MCP

by tbrito88
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Create Construction Plane

create_construction_plane

Create reference planes for sketches in Fusion 360 using offset, angle, midplane, three-point, or tangent methods.

Instructions

Create a construction plane for sketching. Unless a parameter says otherwise, lengths and coordinates are in cm (not mm) and angles in degrees.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
angleNoAngle in degrees (for angle method)
planeNoReference plane (for offset/angle)
methodYes
offsetNoOffset distance in cm (for offset)
edge_nameNoEdge or axis to rotate around (for angle method)
plane_oneNoFirst plane (for midplane)
plane_twoNoSecond plane (for midplane)
point_oneNo[x,y,z] first point
point_twoNo[x,y,z] second point
point_threeNo[x,y,z] third point

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-idempotent, non-destructive operation. The description adds default unit context (cm/degrees) but does not disclose permissions, side effects, or other behavioral traits beyond the 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?

Two sentences, front-loaded with the core purpose and followed by an important default-unit caveat. No filler or redundant information.

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 tool with 10 parameters and five construction methods, the description is minimal. It adds unit context but does not explain method-specific parameter usage, and no output schema exists to cover return behavior.

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 description coverage is 90%, so baseline is 3. The description adds meaningful semantics by clarifying that lengths and coordinates are in cm and angles in degrees unless a parameter overrides this, which supplements point parameters whose schema entries lack unit details.

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?

States a specific verb and resource: 'Create a construction plane for sketching.' An agent can identify the tool's purpose, though the description does not distinguish it from similar siblings like create_construction_axis or create_ucs.

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 explicit when-to-use or when-not-to-use guidance is provided. 'For sketching' hints at context but does not route between alternatives or state prerequisites.

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