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

bambu-printer-mcp

by DMontgomery40
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

reread_ams_rfid

Re-read a Bambu AMS RFID tag for a single slot to refresh filament identity data. Use only when the printer is idle and unloaded, as the operation can move AMS filament.

Instructions

Trigger a Bambu AMS RFID re-read for one AMS slot. X2D on macOS, or Linux with the native helper installed, uses the native official plug-in route. This can move AMS filament; use only when the printer is idle and unloaded.

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": {
      "ams_id": "<ams_id>",
      "slot_id": "<slot_id>"
    },
    "name": "reread_ams_rfid"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostNoHostname or IP of the printer (default: value from env)
ams_idYesAMS unit index from 0 to 3, or 128 for an X2D AMS-HT.
slot_idYesSlot index within that AMS, from 0 to 3
bambu_tokenNoAccess token (default: value from env)
bambu_serialNoSerial number (default: value from env)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.14
    • changedInput schema / properties / ams_id / description
      Previous value: -"AMS unit index from 0 to 3"New value: +"AMS unit index from 0 to 3, or 128 for an X2D AMS-HT."
  2. First observedv1.1.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already disclose non-read-only, non-idempotent, open-world behavior, but they leave destructiveHint=false, which could mislead an agent into thinking nothing physical happens. The description corrects that by warning 'this can move AMS filament,' a side effect no annotation expresses, and adds the platform-dependent execution route. It stops short of describing failure modes or what a successful re-read returns.

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, each load-bearing: the action, the platform route, and the physical-safety precondition. The hazard warning is placed last but not buried, and there is no filler wording.

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 no-output-schema mutation tool, the definition covers action, target granularity, execution route, and physical hazard — enough to call it safely. The remaining gap is outcome expectation: how long the re-read takes and whether it reports tag/filament data on completion is not indicated.

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 the schema already explains ams_id range (0-3, or 128 for X2D AMS-HT), slot_id, and env-backed defaults for host/token/serial. The description adds only the framing 'one AMS slot' and does not elaborate on any parameter meaning, so the baseline 3 applies.

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: 'Trigger a Bambu AMS RFID re-read for one AMS slot,' scoped precisely to a single slot. This clearly separates it from siblings such as get_printer_filaments (read-only lookup), set_ams_drying (AMS operation of a different kind), and resolve_3mf_ams_slots (file-side slot mapping).

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 an explicit precondition — 'use only when the printer is idle and unloaded' — which is exactly the kind of when-to-use guard an agent needs before firing a physical action. It also explains platform routing (X2D on macOS / Linux with native helper), though it does not name a fallback tool for platforms where the native route is unavailable.

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