Skip to main content
Glama
DMontgomery40

bambu-printer-mcp

by DMontgomery40
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

camera_snapshot

Capture a single JPEG frame from a Bambu Lab printer's chamber camera. Returns base64 or saves to disk via save_path; supports A1/P1 TCP and X1/P2S/H2/X2D RTSP.

Instructions

Capture a single JPEG frame from the printer's chamber camera. A1/P1 use TCP-on-6000; X1/P2S/H2/X2D 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)
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_PATH or ffmpeg via $PATH. Per-call overrides require MCP_ALLOW_EXECUTABLE_ARG=1. Required only for the RTSP transport (X1, P2S, H2 series, X2D).
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.14
    • changedInput schema / properties / ffmpeg_path / description
      Previous value: -"Override 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)."New value: +"Override path to the ffmpeg binary used by the RTSP path. Defaults to FFMPEG_PATH or ffmpeg via $PATH. Per-call overrides require MCP_ALLOW_EXECUTABLE_ARG=1. Required only for the RTSP transport (X1, P2S, H2 series, X2D)."
  2. First observedv1.1.1

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the return format (base64 JPEG), the optional disk write, the cold-start delay risk behind timeout_ms, and that ffmpeg overrides require MCP_ALLOW_EXECUTABLE_ARG=1. It stops short of describing error behavior for unsupported models or auth failures.

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?

Three front-loaded sentences, zero filler, and the primary action plus return contract lead. The protocol routing could arguably move to a schema note, but its placement is still efficient.

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?

For an 8-parameter, no-annotation, no-output-schema tool, the description supplies the essential return contract (base64 JPEG, optional disk write) and the transport gotchas. It is nearly complete, lacking only failure-mode detail for unsupported models or token/auth errors.

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 8 parameters, including save_path, timeout_ms, and ffmpeg_path. The description re-states the save_path and base64 return behavior, adding only marginal value beyond the structured fields, which is the baseline-3 case.

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?

States a specific verb and resource: 'Capture a single JPEG frame from the printer's chamber camera.' It also names the protocol split by model, which no sibling tool covers, so an agent can distinguish it immediately from the print-file and STL manipulation siblings.

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

Usage Guidelines3/5

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

The model-to-transport mapping (A1/P1 vs X1/P2S/H2/X2D) is implied usage context, but the description never states when an agent should reach for this tool versus the status/inspection siblings, nor any exclusions or prerequisites beyond the protocol 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