Skip to main content
Glama
DMontgomery40

bambu-printer-mcp

by DMontgomery40
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

bambu_network_call

Call raw FULU BambuNetwork bridge methods with optional injected agent to interact with Bambu cloud services for printer login, handshake, and machine selection.

Instructions

Call a raw FULU OrcaSlicer-bambulab BambuNetwork bridge method, optionally with an initialized network agent injected into the payload.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
methodYesFULU bridge method name, for example bridge.handshake, net.is_user_login, or net.get_user_selected_machine.
payloadNoJSON payload passed to the bridge method.
user_infoNoOptional BambuNetwork user_info JSON string to pass to net.change_user after the agent starts.
timeout_msNoBridge request timeout in milliseconds.
with_agentNoWhen true, initialize a BambuNetwork agent and add its agent id to the payload before calling the method.
country_codeNoBambuNetwork country code, such as US, used by the agent during startup.
bridge_commandNoOverride command for the FULU bridge host or macOS/WSL wrapper; defaults to BAMBU_NETWORK_BRIDGE_COMMAND. Per-call overrides require MCP_ALLOW_EXECUTABLE_ARG=1.
bambu_network_config_dirNoConfig/log directory used by the BambuNetwork agent; defaults to BAMBU_NETWORK_CONFIG_DIR or a user config directory.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.14
    • changedInput schema / properties / bridge_command / description
      Previous value: -"Override command for the FULU bridge host or macOS/WSL wrapper; defaults to BAMBU_NETWORK_BRIDGE_COMMAND."New value: +"Override command for the FULU bridge host or macOS/WSL wrapper; defaults to BAMBU_NETWORK_BRIDGE_COMMAND. Per-call overrides require MCP_ALLOW_EXECUTABLE_ARG=1."
  2. First observedv1.1.1

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It hints that arbitrary bridge methods are invoked ('raw'), but never discloses side effects, permission requirements, risk of destructive methods, or return/error behavior. For an unconstrained low-level call tool this is a significant gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence that conveys the core action and the agent-injection option with no filler. It is tightly sized, though the dense jargon reduces immediate readability.

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

Completeness2/5

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

For an 8-parameter power tool with no annotations and no output schema, the description leaves too much unsaid: which methods are safe, how errors surface, or how it relates to the higher-level Bambu tools. The safety-neutral annotation gap makes this incompleteness more costly.

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 documents all eight parameters in detail. The description adds only a marginal restatement by noting the optional agent injection into the payload. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

The description states a clear verb (call) and resource (raw FULU OrcaSlicer-bambulab BambuNetwork bridge method), and the scope term 'raw' signals it is a low-level escape hatch. It implicitly separates itself from status-oriented siblings like bambu_network_bridge_status, but never names an alternative explicitly.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, nor any reference to the higher-level siblings (print_3mf_bambu_network, start_print). An agent is left to infer that this is the fallback for methods not covered elsewhere, without any statement to that effect.

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