Skip to main content
Glama
Sign In
mcp-server-for-bambu

mcp-server-for-bambu

by b84330808
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Set up printer

setup_printer
Idempotent

Configure the MCP server with a Bambu Lab printer's LAN IP, serial, and access code, then test the live connection and save credentials only after a successful connection.

Instructions

FIRST-TIME SETUP. Configure this MCP server with your Bambu Lab printer's LAN credentials (IP / serial / access code). Tests the connection live and only saves on success. Find the values on the printer touchscreen: Settings → WLAN (IP), Settings → Device → Device Info (serial), Settings → WLAN → LAN Mode Liveview (8-char access code). Make sure LAN Mode Liveview is ON.

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": {
      "ip": "<ip>",
      "serial": "<serial>",
      "access_code": "<access_code>"
    },
    "name": "setup_printer"
  }
}

Input Schema

NameRequiredDescriptionDefault
ipYesPrinter LAN IP address, e.g. 192.168.1.50
serialYesPrinter serial number (15 chars, P1S starts with 01P00A)
access_codeYes8-character LAN access code from the printer's WLAN settings

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only cover the safety profile (idempotent, non-destructive, not read-only); the description adds substantive behavior on top: it tests the connection live before persisting and saves only on success. That failure-atomicity is exactly the kind of fact annotations can't express. It stops short of describing the error surface or where credentials are stored.

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?

Front-loaded with the strongest discriminator ("FIRST-TIME SETUP"), then the action, then the lookup instructions, then the prerequisite. Every sentence supplies information an agent needs; nothing repeats the schema or annotations.

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 mutation tool this is near-complete: it says what is written, that validation is live, and that nothing persists on failure. With no output schema, a brief note on what a failed test returns would close the last gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description earns an upgrade by giving the on-device menu path for each of the three values (IP, serial, 8-char access code), which is operational guidance the schema cannot carry. It adds no format or validation detail beyond what the schema already declares.

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 action (configure the MCP server with printer LAN credentials) plus the exact three values needed, and marks it as FIRST-TIME SETUP, which cleanly separates it from the setup_status sibling. An agent can pick this tool 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?

"FIRST-TIME SETUP" clearly implies this is the initial configuration step rather than a repeat/check operation, and the closing prerequisite (LAN Mode Liveview must be ON) is a real gating condition. It never names setup_status as the follow-up tool, so the routing is implied rather than explicit.

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