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

bambu-printer-mcp

by DMontgomery40
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

camera_stream_stop

Idempotent

Close a printer's camera stream connection and free its cached frames to release resources; other printers keep their own streams.

Instructions

Close this printer's camera connection and free its cached frames. Other printers keep their own streams. Active viewers may restart it; normally let the idle timeout close a shared stream.

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

Input Schema

NameRequiredDescriptionDefault
hostNoPrinter LAN host or IP; defaults to the configured Bambu host.
bambu_tokenNoPrinter LAN access code; defaults to the configured access code.
bambu_serialNoPrinter serial number; defaults to the configured serial and identifies its shared stream.

Output Schema

NameRequiredDescriptionDefault
statusYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.61

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare non-readOnly, idempotent, non-destructive, open-world behavior; the description adds genuine value beyond them by disclosing the side effect (cached frames are freed), the blast radius (only this printer's stream, others unaffected), and a risk (active viewers may restart it). It does not say what happens if no stream is active, but the behavioral picture is otherwise solid.

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?

Three short sentences, front-loaded with the action and its immediate effect, followed by scope and then the caveat. No filler and nothing repeated from the name or schema.

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?

An output schema exists so return values need no explanation, and all three parameters are optional with documented defaults. For a simple lifecycle tool, the description covers action, side effects, scope, and the recommended alternative (idle timeout), leaving nothing an agent needs in order to decide whether to call it.

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 coverage is 100%, so host, token, and serial are already documented including their defaults and the fact that serial identifies the shared stream. The description adds the notion of a 'shared stream' per printer but no parameter-level syntax, format, or fallback detail beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Close this printer's camera connection') plus a secondary effect ('free its cached frames'), which is far more specific than a restated name. It does not explicitly name the sibling camera_stream_start as the counterpart, so the differentiation from camera_frame/camera_snapshot is inferred rather than stated.

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?

Gives real usage steering: 'normally let the idle timeout close a shared stream' is an explicit when-not-to-call rule, and 'active viewers may restart it' warns about a consequence. It lacks an explicit pointer to camera_stream_start for the inverse operation, but the selection context is otherwise clear.

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