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

bambu-printer-mcp

by DMontgomery40
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

list_3mf_plate_objects

Read-onlyIdempotent

Lists each object and copy on a sliced 3MF plate that a Bambu printer can skip, including IDs, names, skip status, and label support, so you can choose IDs for skip_objects during a running print.

Instructions

List the objects of a sliced 3MF plate that the printer can skip, one per copy, as Bambu Studio's skip dialog lists them: identify_id (id), name, whether it is already skipped, and labelObjectEnabled (the plate was sliced with object labels, which skipping needs). Use these ids with skip_objects during a running print.

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": {
      "three_mf_path": "<three_mf_path>"
    },
    "name": "list_3mf_plate_objects"
  }
}

Input Schema

NameRequiredDescriptionDefault
plate_indexNo0-based plate index to inspect (default: 0)
three_mf_pathYesPath to a sliced 3MF/.gcode.3mf file

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety needs no restating. The description adds real context beyond that: the record shape returned (identify_id, name, skipped flag), the one-entry-per-copy behavior matching Bambu Studio's skip dialog, and the meaning of labelObjectEnabled as a prerequisite for skipping.

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?

Two sentences, both earning their place: the first defines scope plus return fields, the second gives the downstream use. Slightly dense with parenthetical asides ('(id)', '(the plate was sliced with object labels, which skipping needs)'), but the essential information is front-loaded.

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?

No output schema exists, and the description compensates by enumerating the returned fields and their meaning, plus the labelObjectEnabled gate the agent must check before skipping. For a simple two-parameter read tool this is nearly complete; only the failure mode on unsliced files or empty plates is unstated.

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 both parameters (three_mf_path, plate_index) are already documented, so the schema carries the load. The description adds only the qualifier that the file must be sliced and that objects are listed per copy; it says nothing about plate_index semantics beyond what the schema states. 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 ('List the objects of a sliced 3MF plate') and narrows it to objects the printer can skip, one per copy. Contrasts implicitly with sibling list_3mf_plates (plates) and skip_objects (action), so an agent can tell which tool returns objects vs. acts on them.

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?

Explicitly routes the agent downstream: 'Use these ids with skip_objects during a running print,' which names the alternative/consumer and the timing condition. The 'sliced 3MF' precondition also implies when the tool is not applicable, though no explicit when-not or unsliced-file fallback is given.

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