Skip to main content
Glama
DMontgomery40

bambu-printer-mcp

by DMontgomery40
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

reread_ams_rfid

Triggers a Bambu AMS RFID re-read for one slot to refresh filament info. Use only when the printer is idle and unloaded because AMS filament may move.

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.

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/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses a key side effect (can move AMS filament) and a safety precondition, though it does not cover auth or reversibility.

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?

Two sentences with no filler. The core action is front-loaded, followed by essential platform and safety notes; every sentence earns its place.

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 tool with no annotations and no output schema, the description is largely complete: it conveys purpose, a critical side effect, and a safety precondition. It omits error handling or expected results, but those are minor for a trigger action.

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 all five parameters are documented. The description adds no parameter-specific meaning beyond what the schema provides, making the baseline of 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: trigger an AMS RFID re-read for one AMS slot. The action is unique among siblings, but no sibling is named to explicitly differentiate it.

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?

Provides a clear precondition ('use only when the printer is idle and unloaded') and notes platform-specific routing. It does not compare against or name alternative AMS-related tools.

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