Skip to main content
Glama
Sign In
Fusion360 Live MCP

Fusion360 Live MCP

by tbrito88
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Create Sketch

create_sketch

Creates a sketch on the XY, YZ, or XZ plane with an optional offset, so you can start 2D geometry on a chosen plane.

Instructions

Create a new sketch on xy/yz/xz plane, optionally offset. Unless a parameter says otherwise, lengths and coordinates are in cm (not mm) and angles in degrees.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_sketch"
  }
}

Input Schema

NameRequiredDescriptionDefault
planeNoxy
z_offsetNoOffset distance from the plane (cm)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare this is a non-readonly, non-idempotent, non-destructive mutation, so the safety profile is covered. The description adds genuinely useful context—units are cm not mm and angles are degrees—but says nothing about what is returned (sketch identity) or what happens on duplicate/failed creation.

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?

Two compact sentences with the core action front-loaded and the units caveat second. Nothing is wasted, though the appended units clause could be tightened.

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 mutation tool with no output schema and only partial param coverage, the unit convention helps but leaves gaps: no return value, no prerequisite design context, no interaction with the sketch's parent body/component.

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 coverage is 50%: z_offset is documented in the schema while plane relies on its enum. The description reinforces the cm unit for lengths/offsets, which is added value, but it does not explain the plane enum or the offset's direction/sign convention.

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+resource (create sketch) and constrains it to the three named planes with an optional offset, so an agent can tell it apart from primitives like create_box or curve tools like draw_line. It does not differentiate itself from the related create_construction_plane sibling, but the resource is unambiguous.

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 when-to-use or when-not-to-use guidance is given; it never says whether this should precede draw_rectangle/draw_line or how it relates to create_construction_plane. The unit convention is the only contextual rule offered.

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