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

bambu-printer-mcp

by DMontgomery40
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

bambu_network_bridge_status

DestructiveIdempotent

Inspect or probe the BambuNetwork bridge runtime to verify cloud and restored printing connectivity; optionally start the bridge and run handshake/agent initialization checks.

Instructions

Inspect or probe the FULU OrcaSlicer-bambulab BambuNetwork bridge runtime used for cloud and restored BambuNetwork printing.

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": "bambu_network_bridge_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
connectNoWhen true, start the bridge command and run a handshake plus agent initialization probe.
user_infoNoOptional BambuNetwork user_info JSON string to pass to net.change_user after the agent starts.
timeout_msNoBridge request timeout in milliseconds for the connect probe.
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 readOnlyHint=false, destructiveHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is partly covered. The description adds that the runtime relates to cloud and restored printing, but it does not disclose that connect=true spawns a bridge process, what the handshake probe does, or why a destructive hint is attached to something described as "inspect" — that tension deserves explicit wording.

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 filler, which is appropriately sized. Its weakness is under-specification rather than verbosity, and the internal jargon ("FULU OrcaSlicer-bambulab") costs a little 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?

This is a six-parameter tool that can spawn an external executable override and carries destructiveHint=true, yet the description is one sentence with no output description and no risk or sequencing information. For that complexity level, far more context is needed than what is present.

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 every parameter including the MCP_ALLOW_EXECUTABLE_ARG=1 caveat on bridge_command is already documented in structured data. The description adds no meaning beyond the schema — no explanation of how user_info interacts with the connect probe or what timeout_ms applies to.

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?

"Inspect or probe the ... BambuNetwork bridge runtime" gives a verb and a resource, but "inspect or probe" is a hedged, fuzzy pair that leaves unclear what the tool actually returns (a status snapshot? a handshake result?). It also never distinguishes this from the sibling bambu_network_call, which an agent would reasonably consider for the same bridge.

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 guidance at all: nothing says whether to call this before bambu_network_call, whether it is a prerequisite for print_3mf_bambu_network, or when to set connect=true versus omitting it. The phrase "used for cloud and restored BambuNetwork printing" hints at a context but states no selection rule or prerequisite.

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