Skip to main content
Glama
JohanRouyer

Bambu Studio Advisor

by JohanRouyer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

List presets

list_presets
Read-onlyIdempotent

Lists Bambu Studio process, filament, and machine presets with source and parent details, helping you find an exact preset name before comparing or slicing.

Instructions

List Bambu Studio presets of one type, with their source and parent. Read-only. Use it to find an exact preset name before get_preset, compare_presets or slicing; use material_guide instead to get the recommended filament preset for a material.

Input Schema

NameRequiredDescriptionDefault
kindYesPreset type: "process" (print settings), "filament" or "machine" (printer).
searchNoWords that must all appear in the preset name, e.g. "PLA Matte".
sourceNo"user" (presets the user saved), "system" (Bambu presets) or "all".user
printer_nameNoKeep only presets compatible with this machine preset; "default" = the user's default printer, null = every printer.default

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.0.1
    • addedInput schema / properties / kind / description
      Added value: +"Preset type: \"process\" (print settings), \"filament\" or \"machine\" (printer)."
    • addedInput schema / properties / printer_name / description
      Added value: +"Keep only presets compatible with this machine preset; \"default\" = the user's default printer, null = every printer."
    • addedInput schema / properties / search / description
      Added value: +"Words that must all appear in the preset name, e.g. \"PLA Matte\"."
    • addedInput schema / properties / source / description
      Added value: +"\"user\" (presets the user saved), \"system\" (Bambu presets) or \"all\"."
  2. First observedv1.0.0

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the "Read-only" sentence restates structured data. The only added context is that results carry source and parent, which is return-value information the output schema already covers; nothing is said about result size or ordering.

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?

Two short sentences, zero filler, with the scope constraint front-loaded before the routing to alternatives.

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?

With annotations covering safety, an output schema covering returns, and full parameter documentation, the description supplies what is needed to select and call the tool. Minor gaps such as result ordering or limits are not essential to invocation.

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% with two enums, so the schema fully documents kind, search, source and printer_name. The description adds no syntax or default behavior beyond that, so the 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 Bambu Studio presets of one type") plus the returned fields (source and parent), and explicitly marks it read-only. It is clearly distinguishable from get_preset, which fetches a single preset.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Names the downstream tools this enables (get_preset, compare_presets, slicing) and the condition to use it (finding an exact preset name). It also names an alternative, material_guide, and the situation that selects it.

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