Skip to main content
Glama
Sign In
Fusion360 Live MCP

Fusion360 Live MCP

by tbrito88
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Extend Curve

extend_curve

Extend a sketch curve to the nearest intersection, starting from the end nearest a given point. Use to close gaps or connect curves in CAD sketches.

Instructions

Extend a sketch curve to the nearest intersection. The end nearest to the given point is extended. Unless a parameter says otherwise, lengths and coordinates are in cm (not mm) and angles in degrees.

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": {
      "curve_index": "<curve_index>",
      "point_x": "<point_x>",
      "point_y": "<point_y>"
    },
    "name": "extend_curve"
  }
}

Input Schema

NameRequiredDescriptionDefault
point_xYesX near the end to extend
point_yYesY near the end to extend
curve_indexYesIndex of the curve to extend
sketch_nameNo

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 already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the description's job is supplementary. It usefully discloses the unit convention (cm not mm, angles in degrees) and which end is affected, but says nothing about the non-idempotent character of repeated calls or what happens when no intersection exists in the extension direction.

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 with no filler, and the core action is front-loaded ahead of the units caveat. Every clause carries information an agent needs.

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?

No output schema exists and the tool has a mutation with a non-idempotent hint, yet the description omits failure behavior (no intersection found, point not near a curve end) and leaves sketch_name entirely undocumented. The units clarification helps, but the definition is not complete for a 4-parameter editing operation.

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 75%, so the point_x/point_y/curve_index meanings are already documented in the schema. The description adds only the global unit convention; it does not explain the undocumented sketch_name parameter or how the point relates to curve selection beyond the schema's own wording.

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 ('Extend a sketch curve') plus the precise scope of the action ('to the nearest intersection'), which lets an agent distinguish it from trim_curve or offset_curve. It stops short of naming any sibling explicitly, so it is clear but not fully differentiated.

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 choose this over trim_curve or offset_curve, and no prerequisites or preconditions (e.g. sketch must be active or in edit mode are never mentioned). The only usage-like content is the mechanical note that the end nearest the given point is extended, which describes behavior rather than when-to-use.

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