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

bambu-printer-mcp

by DMontgomery40
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

list_printer_files

Read-onlyIdempotent

Lists files stored on a Bambu Lab printer, enabling users to inspect available models and manage print jobs from Claude.

Instructions

List files stored on the Bambu Lab printer

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

Input Schema

NameRequiredDescriptionDefault
hostNoHostname or IP of the printer (default: value from env)
bambu_tokenNoAccess token (default: value from env)
bambu_serialNoSerial number (default: value from env)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered. The description adds essentially nothing beyond them: it does not say which storage location is read (internal memory, SD card, AMS), whether results are paginated or truncated, or whether a connection/authentication with the printer must be live.

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?

A single front-loaded sentence with no redundant wording. Its brevity is efficient rather than padded, though it is arguably terse to the point of under-specification for a networked read tool.

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?

For a simple read tool the annotations and schema cover safety and inputs, but with no output schema the description should indicate what the listing contains (file names, paths, sizes) so the agent can chain into inspect_print_file or delete_printer_file. That return-shape information is entirely absent.

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% and all three parameters (host, bambu_token, bambu_serial) are documented with environment-variable defaults, so the schema does the heavy lifting. The description adds no meaning about how host/serial select the target printer, making the baseline 3 appropriate.

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 ("List files") scoped to the Bambu Lab printer, so an agent can tell it retrieves a file listing rather than printing or deleting. It does not distinguish itself from close siblings such as list_3mf_plate_objects or inspect_print_file, so it stops short of a 5.

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?

There is no guidance on when to use this versus alternatives like inspect_print_file, list_3mf_plate_objects, or upload_file/delete_printer_file workflows. The agent must infer that this is the discovery step before those tools, with nothing stated about prerequisites or exclusions.

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