fusion-reconstruct-mcp

Overview Schema Source Related Servers Discussions Admin

fusion_get_timeline

Retrieve the feature timeline of a reconstructed Fusion 360 model, listing creation order, name, type, and suppressed state to verify the modeling history.

Instructions

List the feature timeline (creation order, name, type, suppressed state) - Fusion's own record of every feature created so far.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 21, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are provided, and the prose discloses no behavioral constraints: there is no mention that it is a read-only query, no mention of how 'suppressed' features are displayed/output, and no edge cases for huge timelines or permissions. The availability of safety information is unknown.

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 compact sentences; no wasted words; the element order is listed clearly.

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?

For a zero-parameter, no-output-schema query operation, the listed fields and the record scope are sufficient for purpose, but it does not explain output format, possible ordered return, or behavior on suppressed features. Overall, reasonably complete, but still some gaps.

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

Parameters4/5

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

The tool accepts zero parameters and the schema covers 100% of inputs, so there are no parameter semantics gaps to fill.

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?

Description uses a specific action verb 'List' on the 'feature timeline (creation order, name, type, suppressed)', and identifies it as Fusion's own full record of every feature created. It lacks an explicit alternative tool when the intended use is unclear, and 'suppressed' is not defined, but the resource is distinct enough for a 4.

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 gives context ('Fusion's own record of every feature created so far') but does not provide explicit guidance on when to use this tool versus other listing tools, nor does it state exclusions or alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.