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

self-host-fusion360-mcp

by mystify59
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

fusion_measure_angle

Read-only

Calculates the angle in degrees between the first faces of two selected bodies in a Fusion 360 model.

Instructions

Angle (degrees) between the first faces of two bodies.

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_a": "<body_a>",
      "body_b": "<body_b>"
    },
    "name": "fusion_measure_angle"
  }
}

Input Schema

NameRequiredDescriptionDefault
body_aYes
body_bYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, making the non-destructive nature clear. The description adds that it returns degrees but does not clarify behavior for bodies with no faces or how 'first faces' are determined, leaving some ambiguity.

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 very concise with a single sentence, no redundancy. However, it sacrifices detail for brevity, earning a high but not perfect score.

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?

Given the tool's simplicity and no output schema, the description is somewhat complete for basic understanding but lacks details on parameter types, units, and edge cases. It meets the minimum viable bar.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description mentions 'two bodies' but does not explain that body_a and body_b can be integer IDs or string names. With 0% schema description coverage, the description adds minimal value beyond the parameter names.

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 tool measures the angle between the first faces of two bodies, which is a specific verb and resource. It distinguishes itself from sibling tools like fusion_measure_distance by specifying angle rather than distance.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when an angle measurement is needed, but does not provide explicit guidance on when to use this tool over alternatives (e.g., fusion_measure_distance) or conditions like body face availability.

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