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

bambu-printer-mcp

by DMontgomery40
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

list_templates

Read-onlyIdempotent

Lists saved slicing templates from the local template registry so you can find and choose existing print settings before slicing. Supports an optional template directory override.

Instructions

List saved slicing templates from the local template registry directory.

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

Input Schema

NameRequiredDescriptionDefault
template_dirNoOptional template directory override. Defaults to BAMBU_TEMPLATE_DIR or the server's configured local template registry.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety and locality profile is covered. The description adds the concrete storage location ("local template registry directory"), which is useful context beyond the annotations, but says nothing about ordering, pagination, or what happens when the directory is empty or missing.

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 filler or redundancy; the resource and scope come first. It is efficient but leaves no room for the routing or return-shape details an agent would benefit from.

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, zero-required-parameter read tool with full schema coverage and complete annotations, the description is minimally sufficient. The remaining gap is that no output schema exists and the description does not indicate what a template entry looks like (name, id, path), which an agent needs to chain into slice_with_template.

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 template_dir is already documented in the schema with its BAMBU_TEMPLATE_DIR fallback chain. The description adds no further meaning about the override parameter, so the baseline 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?

States a specific verb and resource ("List saved slicing templates") plus a scope qualifier ("from the local template registry directory"), which separates it from file-listing siblings like list_printer_files and list_3mf_plate_objects. It does not, however, explicitly name a sibling or contrast itself with save_template / slice_with_template.

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 when-to-use or when-not-to-use guidance, no mention of prerequisites, and no pointer to slice_with_template as the natural consumer of the listed templates. The only hint is the word "saved", which weakly implies discovering templates before using them.

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