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

bambu-printer-mcp

by DMontgomery40
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

counterpart_setup_fields

Read-onlyIdempotent

Lists supported printer models and .env setup fields, including aliases, required flags, and model choices; pass a serial number to identify its model. Reads no values and sends nothing to a printer.

Instructions

Counterpart contract (counterpart/1): the printers this server drives and the settings it reads for each, by .env variable name (first canonical, then aliases): label, hint, whether required, the model choices and the model each serial-number prefix names. Pass serial to get the model it names. Sends nothing to a printer and returns no configured values.

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": "counterpart_setup_fields"
  }
}

Input Schema

NameRequiredDescriptionDefault
serialNoA Bambu serial number: model is the one it names, when known.

Output Schema

NameRequiredDescriptionDefault
kindsYes
modelNo
serverYes
slicerNo
contractYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.77

TDQS

B3.1/5.0
Behavior4/5

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

The annotations already mark this as read-only, idempotent, non-destructive, and closed-world, and the description adds useful behavioral context: it sends nothing to a printer and returns no configured values. That clarifies side effects and output scope beyond the annotations, though it does not discuss any auth or rate-limit behavior.

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?

The description is compact and front-loads the contract definition, then parameter behavior, then safety context. A few phrases are dense and slightly redundant, but every sentence contributes relevant information.

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?

With an output schema and rich annotations, the description need not explain return values, and it does explain that no configured values are returned. However, it remains unclear when this tool should be selected over the many printer-discovery and printer-info siblings, leaving a meaningful contextual gap.

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 the single optional serial parameter is already well documented. The description's "Pass serial to get the model it names" largely repeats the schema description rather than adding new semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the resource as the counterpart setup contract and lists field categories, but it is not verb-led and the phrase "Counterpart contract (counterpart/1)" is jargon. An agent can infer it describes setup-field metadata, but the core action (returning a contract/schema, not configured values) is not stated as directly as it could be.

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?

The only usage guidance is "Pass serial to get the model it names." There is no explicit when-to-use guidance, no when-not-to-use guidance, and no differentiation from siblings such as counterpart_discover_printers or counterpart_printer_info.

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