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

bambu-printer-mcp

by DMontgomery40
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_printer_status

Read-onlyIdempotent

Retrieve current Bambu Lab printer status to check readiness and progress; optionally specify host, access token, and serial, or use environment defaults.

Instructions

Get the current status of 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": "get_printer_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostNoHostname or IP address of the printer (default: value from env)
bambu_tokenNoAccess token for the Bambu Lab printer (default: value from env)
bambu_serialNoSerial number for the Bambu Lab printer (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, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds nothing further — no mention of what the status contains, whether it reflects live telemetry or cached state, latency, or failure behavior when the printer is offline — so it earns little credit beyond the annotations.

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. It is efficient, though its brevity borders on under-specification that is penalized in other dimensions rather than here.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only status call with fully documented parameters and complete annotations, the essentials are present. Still, with no output schema and no description of what status information is returned, the agent cannot anticipate the response shape or handle offline/error cases.

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 each of the three optional parameters (host, bambu_token, bambu_serial) is documented in the schema with its env default. The description adds no meaning beyond that, so the baseline of 3 applies.

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?

The description names a specific verb and resource ('Get the current status of the Bambu Lab printer'), so its function is unambiguous. However, it does nothing to distinguish itself from closely related siblings such as counterpart_printer_info, get_printer_filaments, or bambu_network_bridge_status.

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 tool versus the numerous other printer-state siblings, and no stated prerequisites or exclusions. The agent must infer usage purely from the name.

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