bambu-printer-mcp

Overview Schema Source Related Servers Discussions Admin

fusion_mcp_new_design

Creates a new parametric Fusion design document so subsequent modeling tools have an active design to work on. Optionally imports an F3D source file or binds an isolated document session.

Instructions

Open a new parametric design document in Fusion (execute_code with app.documents.add(FusionDesignDocumentType)). The Fusion MCP tools work on the open design, so a design pass calls this first.

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_mcp_new_design"
  }
}

Input Schema

Name	Required	Description
`source_f3d`	No	With bind_document, import this absolute F3D path into a new document for revision.
`timeout_ms`	No	Total deadline in milliseconds; defaults to FUSION_MCP_TIMEOUT_MS or 180000.
`bind_document`	No	Create an isolated document and return its session identity, restoring the previously active document. Requires document-binding support in the configured bridge/add-in.

Output Schema

Name	Required	Description	Default
`status`	Yes
`document`	Yes
`parametric`	Yes
`document_id`	No
`document_binding`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv1.1.61Nov 5, 2026

addedInput schema / properties / bind_document

Added value: +{
+  "description": "Create an isolated document and return its session identity, restoring the previously active document. Requires document-binding support in the configured bridge/add-in.",
+  "type": "boolean"
+}

addedInput schema / properties / source_f3d

Added value: +{
+  "description": "With bind_document, import this absolute F3D path into a new document for revision.",
+  "type": "string"
+}

addedOutput schema / properties / document_binding

Added value: +{
+  "const": 1,
+  "type": "integer"
+}

addedOutput schema / properties / document_id
```
Added value: +{
+  "type": "string"
+}
```

Addedv1.1.51Nov 2, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare this is not read-only, not destructive, and not idempotent, which matches opening a new document. The description adds meaningful behavioral context beyond those annotations by explaining that subsequent Fusion MCP operations depend on the open design and that this tool establishes it.

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 and front-loads the core action, with the sequencing guidance second. There is no redundant or wasted wording.

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 annotations, a complete parameter schema, and an output schema, the description supplies the essential purpose and sequencing needed to call this correctly. It could be stronger with explicit guidance about existing open designs and alternatives, but nothing critical is missing.

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 description coverage is 100%, so the input schema already documents source_f3d, timeout_ms, and bind_document. The description mentions the underlying app.documents.add call but does not add meaning about the individual parameters beyond what the schema provides.

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 states a specific verb and resource: "Open a new parametric design document in Fusion," and includes the underlying API call. It also distinguishes this setup step from the broader Fusion MCP tools by explaining that a design pass calls it first.

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 gives clear usage context: Fusion MCP tools operate on the open design, so this should be called first during a design pass. It does not explicitly say when not to use it, such as when a design is already open, nor does it name a specific alternative to use instead.

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

Deploy Server