fusion-reconstruct-mcp

Overview Schema Source Related Servers Discussions Admin

fusion_set_parameter

Sets or updates a Fusion 360 user parameter by name and expression for maintaining a readable parameter table.

Instructions

Create (or update) a Fusion user parameter, e.g. name="wall_thickness", expression="3 mm". Reference it in later calls' numeric fields is not supported over this bridge (those stay plain numbers) - this is for keeping the design's parameter table meaningful for a human opening it afterwards.

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": {
      "name": "<name>",
      "expression": "<expression>"
    },
    "name": "fusion_set_parameter"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes
`expression`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 21, 2026

TDQS

A4.4/5.0

Behavior4/5

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

No annotations provided, so the description carries the burden. It discloses that the tool creates or updates parametersholidays and explicitly states that referencing in later numeric fields is not supported – a key behavioral trait. It doesn't mention side effects or permissions, but for a simple setter, this is acceptable. It goes beyond just saying

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?

The description is two sentences, clearly structured: first states the action with an example, second explains the limitation and purpose. Every sentence adds value, no fluff.

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 two-parameter tool with no output schema tricks, the description covers the essential purpose, the create/update behavior, and a key limitation. It's sufficient for an agent to understand when and how to use it. Could mention that it also updates existing parameters, but that's implied by 'Create (or update)'. Overall, complete enough.

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?

Schema coverage is 0%, but the description provides an example that clarifies both parameters: name and expression (with value format). That gives the agent sufficient context to understand the semantics without needing schema descriptions. The example is concrete and helpful.

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 action: 'Create (or update) a Fusion user parameter' with an explicit example. It distinguishes itself from other fusion tools by explaining its specific purpose (maintaining a parameter table) and a limitation (no referencing later). This is specific verb+resource with clear scope.

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?

It explains when to use it (to keep the parameter table meaningful for a human) and explicitly warns about a limitation (not supported for numeric field references). It doesn't compare to direct siblings like fusion_list_parameters, but given the context of many fusion_* sibling tools, it's clear enough. No explicit exclusions, but the limitation serves as a

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