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

self-host-fusion360-mcp

by mystify59
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

fusion_sketch_offset

Offsets a sketch curve (by index) a set distance toward a specified direction vector, enabling precise geometry adjustments.

Instructions

Offset a sketch curve (by index) by distance mm toward (dir_x, dir_y).

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": {
      "sketch": "<sketch>",
      "curve": "<curve>",
      "distance": "<distance>"
    },
    "name": "fusion_sketch_offset"
  }
}

Input Schema

NameRequiredDescriptionDefault
curveYes
dir_xNo
dir_yNo
sketchYes
distanceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

B3.1/5.0
Behavior2/5

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

The description says 'offset' but does not clarify whether the original curve is modified or a new offset curve is created. Annotations indicate readOnlyHint=false and destructiveHint=false, yet the description adds no additional behavioral context such as side effects or required permissions.

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?

The description is a single concise sentence with essential information: verb, resource, and key parameters. No unnecessary words, though it could benefit from slight elaboration on parameter roles.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is a sketch modification operation with no output schema. The description is minimal and does not explain return value (if any), error conditions, or behavior when parameters are invalid. This is insufficient for a CAD operation with multiple parameters.

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 0%, but the description explains 'distance mm' and 'toward (dir_x, dir_y)', giving meaning to these parameters. However, 'curve' (integer index) and 'sketch' (ID) are not explained, so the benefit is partial.

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 the verb 'offset', the resource 'a sketch curve (by index)', and the parameters 'distance mm' and 'toward (dir_x, dir_y)'. It is specific and distinguishes from other sketch tools like line or circle.

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 is provided on when to use this tool versus other sketch tools or alternatives. Prerequisites (e.g., sketch must exist, valid curve index) are not mentioned.

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