Skip to main content
Glama
ceweldy

Bambu Printer MCP

by ceweldy

camera_snapshot

Capture a single JPEG frame from a Bambu printer's chamber camera. Returns base64 or saves to disk. Supports A1, P1, X1, P2S, H2 models.

Instructions

Capture a single JPEG frame from the printer's chamber camera. A1/P1 use TCP-on-6000; X1/P2S/H2 use RTSP via ffmpeg. Returns JPEG as base64; pass save_path to also write the bytes to disk.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hostNoHostname or IP of the printer (default: value from env)
printerNoConfigured printer ID. Omit to use the default printer or the only configured printer.
save_pathNoOptional absolute path to write the JPEG to disk. If omitted, only the base64 payload is returned.
timeout_msNoMax ms to wait for a full frame (default 8000). Camera may take a few seconds on cold start.
bambu_modelNoPrinter model. Used to route to the correct protocol or fail fast on unsupported models. Defaults to BAMBU_MODEL.
bambu_tokenNoAccess token (default: value from env)
ffmpeg_pathNoOverride path to the ffmpeg binary used by the RTSP path. Defaults to ffmpeg via $PATH. Required only for the RTSP transport (X1, P2S, H2 series).
bambu_serialNoSerial number (default: value from env)
experimentalNoDeprecated and ignored. Earlier this flag let callers probe H2 series via the A1/P1 TCP-on-6000 path; live testing on an H2S confirmed H2 uses RTSP instead, so the flag has no effect now.
Behavior5/5

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

With no annotations, the description carries full burden and discloses key traits: protocol differences, output format, optional disk write, timeout behavior, and cold start delay. No contradictions.

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?

Two sentences with front-loaded main action and output. Every sentence is informative with no waste. Efficient and clear.

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

Completeness4/5

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

The description covers the core behavior, output, and protocol differences. It lacks details on error handling or authentication, but given the schema covers parameter descriptions, it is mostly complete for a snapshot tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds value by summarizing the protocol routing based on 'bambu_model' and noting the 'experimental' parameter is deprecated, which goes beyond the schema.

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 clearly states the action ('Capture a single JPEG frame'), the specific resource ('printer's chamber camera'), and the output format ('Returns JPEG as base64'). It distinguishes from sibling tools as none are camera-related.

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

Usage Guidelines4/5

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

The description provides clear context on when to use based on printer model (A1/P1 vs X1/P2S/H2) via protocol details, but does not explicitly state when not to use or list alternative tools. The deprecated flag guidance is useful.

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