Skip to main content
Glama
Sign In
bambu-printer-mcp

bambu-printer-mcp

by DMontgomery40
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

fusion_mcp_call

Destructive

Calls a discovered Fusion MCP tool by name with matching arguments, preserving full MCP content and errors. Discover schemas first and use an open design before modifying it.

Instructions

Call a discovered tool on the configured Fusion MCP server, such as create_sketch, extrude, fillet, create_parameter, set_parameter, check_interference or execute_code, preserving its full MCP content and errors. Discover tool schemas with fusion_mcp_status first. Calls change the open Fusion design and are never automatically retried. Most tools need an open design: call fusion_mcp_new_design first.

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": {
      "tool_name": "<tool_name>"
    },
    "name": "fusion_mcp_call"
  }
}

Input Schema

NameRequiredDescriptionDefault
argumentsNoArguments matching the remote tool's discovered input schema.
tool_nameYesExact tool name advertised by the Fusion MCP server.
timeout_msNoTotal deadline in milliseconds; defaults to FUSION_MCP_TIMEOUT_MS or 180000.
document_idNoSession identity returned by a bound new design. Every operation targets this document, even if the user changes tabs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.1.61
    • addedInput schema / properties / document_id
      Added value: +{
+  "description": "Session identity returned by a bound new design. Every operation targets this document, even if the user changes tabs.",
+  "minLength": 1,
+  "type": "string"
+}
    • changedOutput schema / (root)
      Previous value: -{
-  "type": "object"
-}New value: +null
  2. Addedv1.1.51

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare destructive/non-idempotent/open-world, and the description adds value beyond them: calls mutate the open Fusion design, are never auto-retried, preserve the remote tool's full MCP content and errors, and require an open design. That is exactly the operational context an agent needs before firing a remote destructive call.

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?

Four sentences, each carrying distinct load: what it does, schema-discovery prerequisite, mutation/no-retry warning, design prerequisite. The purpose is front-loaded and there is no filler.

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

Completeness5/5

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

For a destructive, open-world proxy tool with no output schema, it covers the prerequisites, mutation consequences, retry semantics, error pass-through and default timeout. Nothing an agent needs to invoke it safely appears to be 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 schema already explains tool_name, arguments, timeout_ms and document_id; the description adds only indirect context (that a bound design gates calls). Baseline 3 is appropriate since the description does not add per-parameter syntax or format detail.

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 ('Call a discovered tool on the configured Fusion MCP server') and enumerates concrete examples (create_sketch, extrude, fillet, execute_code). It is clearly separable from fusion_mcp_status (discovery) and fusion_mcp_new_design (setup), which are named explicitly.

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

Usage Guidelines5/5

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

Gives explicit ordering rules: discover schemas with fusion_mcp_status first, and open a design with fusion_mcp_new_design before calling most tools. It also states the call is never automatically retried, which tells the agent to handle failure itself rather than loop.

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