Skip to main content
Glama
ceweldy

Bambu Printer MCP

by ceweldy

bambu_network_call

Execute raw FULU bridge methods to interact with Bambu Lab's network, optionally initializing a network agent for authenticated requests.

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.
bambu_network_config_dirNoConfig/log directory used by the BambuNetwork agent; defaults to BAMBU_NETWORK_CONFIG_DIR or a user config directory.
Behavior2/5

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

With no annotations, the description must fully convey behavioral traits. It mentions the raw nature and optional agent injection but fails to disclose destructiveness, authentication needs, side effects, or rate limits, leaving significant gaps.

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 a single, front-loaded sentence with no waste. It conveys the essential purpose efficiently, earning top marks for conciseness.

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?

Given the tool has 8 parameters (including nested objects) and no output schema, the one-sentence description is insufficient. It does not explain how to compose payloads, what methods are valid, or the implications of with_agent, leaving the agent under-informed.

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 parameters. The tool description adds no additional parameter context beyond what the schema provides, thus baseline score of 3 is appropriate.

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 uses a specific verb ('call') and identifies the exact resource ('raw FULU OrcaSlicer-bambulab BambuNetwork bridge method'), clearly distinguishing it from higher-level sibling tools like print, slice, or bambu_network_bridge_status.

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?

No guidance is provided on when to use this tool versus alternatives in the sibling list, such as using a dedicated higher-level tool instead of a raw bridge method, or any prerequisites or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ceweldy/bambu-printer-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server