Skip to main content
Glama
Sign In
Fusion360 MCP Server

Fusion360 MCP Server

by shinobi81
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

List Edges

list_edges
Read-onlyIdempotent

Retrieve a body's edges with index, endpoints, midpoint, length, and curve type so you can supply valid edge indices to fillet and chamfer.

Instructions

List a body's edges with index, endpoints, midpoint, length and curve type; the indices are what fillet and chamfer take as edge_indices

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": "list_edges"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum edges returned; count is the real total
body_nameNoBody name (default: the body at body_index)
body_indexNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered by structured data. The description usefully adds the returned field set and the downstream identifier contract, but says nothing about ordering, truncation, or the total-count information implied by the limit parameter's schema text.

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?

A single sentence that front-loads the action and the payload, then closes with the reason the tool matters. Nothing is redundant and the semicolon cleanly separates capability from downstream use.

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

Completeness4/5

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

With no output schema, the description carries the burden of describing returns and does so by naming all five fields, including the crucial index. It falls short only on how many edges come back and how the real total is surfaced, which is a moderate gap for a listing tool with a limit parameter.

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 never mentions limit, body_name, or body_index; 'a body's edges' only weakly gestures at the body selector. With schema coverage at 67% and body_index carrying no description at all, the description does not compensate for the documented gap or explain the default body behavior.

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?

States a specific verb and resource ('List a body's edges') and enumerates exactly what each entry contains (index, endpoints, midpoint, length, curve type). It also distinguishes itself functionally from siblings by declaring its role as the index provider for fillet and chamfer, so an agent can tell why it would call this rather than a geometry-mutation tool.

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

Usage Guidelines4/5

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

The clause about indices being what fillet and chamfer take as edge_indices makes the intended workflow clear: call this first to discover edge indices, then pass them to those tools. There is no explicit exclusion or 'when not to use' guidance, and no mention of what to do if the body has no edges, but the contextual trigger is strong.

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