bambu-printer-mcp

Overview Schema Source Related Servers Discussions Admin

delete_printer_file

DestructiveIdempotent

Deletes a file from a Bambu Lab printer's SD card over FTPS, requiring confirm:true and allowing only cache/, timelapse/, and logs/ paths.

Instructions

Delete a file from the Bambu Lab printer's SD card via FTPS. Destructive: requires confirm:true. Restricted to cache/, timelapse/, and logs/ directories. Path traversal segments (..) are rejected.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "filename": "<filename>"
    },
    "name": "delete_printer_file"
  }
}

Input Schema

Name	Required	Description
`host`	No	Hostname or IP of the printer (default: value from env)
`confirm`	No	Must be true to actually delete. When false or omitted the call returns without sending an FTP request.
`filename`	Yes	File to delete. Bare names default to cache/<name>; pass a relative path like timelapse/foo.mp4 to target other allowed directories.
`bambu_token`	No	Access token (default: value from env)
`bambu_serial`	No	Serial number (default: value from env)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.1May 17, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already flag destructiveHint and idempotentHint, but the description adds real context beyond them: the confirm:true gate, the directory sandbox, and path-traversal rejection. It does not disclose what happens on a missing file or whether failures are silent, which keeps it below a 5.

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?

Four short sentences, safety-critical information front-loaded ('Destructive: requires confirm:true') and constraints following immediately. No filler or redundant restatement of the tool name.

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 a destructive remote-filesystem tool with no output schema, the definition covers operation, transport, confirmation, directory scope, and traversal defense — enough to call it correctly. Missing only failure-mode behavior (nonexistent file, auth failure) and any note on what a successful call returns.

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 every parameter is documented there, including the confirm gate and the filename path-resolution rule, so the schema carries the load. The description only restates confirm:true and the directory constraint in summary form rather than adding new parameter-level meaning.

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 — 'Delete a file from the Bambu Lab printer's SD card via FTPS' — including the transport, which distinguishes it from siblings like list_printer_files, upload_file, or inspect_print_file. An agent can identify the operation without opening the schema.

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 concrete preconditions (confirm:true required, allowed directories limited to cache/, timelapse/, logs/) that govern when the call will actually succeed. It does not name alternatives such as list_printer_files for verifying existence before deleting, so it stops just short of explicit when-vs-alternative routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server