Skip to main content
Glama
rowbotik

bambu-printer-mcp

camera_snapshot

Capture a single JPEG frame from your Bambu Lab printer's chamber camera. Returns base64 encoded image, with optional direct file save.

Instructions

Capture a single JPEG frame from the printer's chamber camera. TCP-on-6000 protocol (per OpenBambuAPI/video.md) — verified upstream for A1, A1 mini, P1S, P1P. X1/P2S use RTSP and are not yet supported. H2 series is undocumented and rejected with a clear error. Returns JPEG as base64; pass save_path to also write the bytes to disk.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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.
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.
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).
hostNoHostname or IP of the printer (default: value from env)
bambu_serialNoSerial number (default: value from env)
bambu_tokenNoAccess token (default: value from env)
Behavior5/5

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

With no annotations, the description fully discloses behavioral traits: protocol details, model support and rejection, return format (base64), optional disk writing, timeout behavior, deprecation of experimental flag, and conditional requirement for ffmpeg_path. This is comprehensive.

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 concise, front-loading the main action ('Capture a single JPEG frame'), then efficiently adding technical details in subsequent sentences. No superfluous information.

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

Completeness5/5

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

Given 8 parameters (0 required), no output schema, and no annotations, the description provides thorough context: protocol, model support, return format, parameter behavior, and failure modes. It leaves no critical gaps for an AI agent to use the tool correctly.

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

Parameters5/5

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

The description adds significant meaning beyond the input schema: explains save_path's effect on return value, timeout_ms cold start context, deprecation of experimental, and conditional requirement of ffmpeg_path. Schema coverage is 100%, and the description enriches every parameter.

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 specifies the tool captures a single JPEG frame from the printer's chamber camera. It identifies the protocol (TCP-on-6000) and supported models (A1, A1 mini, P1S, P1P). The verb 'Capture' and resource 'single JPEG frame' are specific and distinct from sibling tools.

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 guidance on model compatibility (supported vs. unsupported) and optional parameters like save_path. However, it does not explicitly state when to use this tool versus alternatives, but given no sibling camera tool, this is acceptable.

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/rowbotik/bambu-printer-mcp'

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