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

bambu-printer-mcp

by DMontgomery40
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

bambu_network_call

DestructiveIdempotent

Invoke a raw FULU BambuNetwork bridge method to query or control Bambu printer network functions, optionally injecting an initialized network agent into the request payload.

Instructions

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

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": {
      "method": "<method>"
    },
    "name": "bambu_network_call"
  }
}

Input 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.8/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, readOnlyHint=false and idempotentHint=true, so the safety profile is covered structurally. The description adds the meaningful signal that this is a "raw" unrestricted bridge call that can optionally spin up a BambuNetwork agent, but it says nothing about side effects of arbitrary methods, startup cost of the agent, or whether the agent persists between calls.

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 with no padding or repetition. It is compact, though the dense jargon string ("FULU OrcaSlicer-bambulab BambuNetwork bridge") is opaque enough to slightly hurt first-read clarity.

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, open-world, destructive passthrough tool with no output schema, the description is thin: it does not describe what the bridge returns, how errors surface, or whether network-agent initialization has lasting state. An agent would need to infer most operational behavior from the schema alone.

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 all eight parameters including the agent injection, timeout and bridge_command override are already documented. The description adds only the fact that agent injection is conditional, which the schema's with_agent field already states, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource ("Call a raw FULU OrcaSlicer-bambulab BambuNetwork bridge method"), so an agent knows this is a generic dispatch/passthrough tool. However it never distinguishes itself from the sibling bambu_network_bridge_status or print_3mf_bambu_network, so an agent cannot tell which entry point to pick without reading schemas.

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, no mention of alternatives for higher-level operations, and no prerequisites such as needing the bridge host running. The only contextual hint is the parenthetical about optionally injecting an initialized agent, which is about a parameter rather than routing.

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