Skip to main content
Glama
Sign In
Slicewise

Slicewise

by gjlmotea
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Save a user preset to Bambu Studio

bambu_save_user_preset

Creates a custom Bambu Studio preset that inherits from a system preset, letting AI-tuned parameters appear in the GUI after restart while preventing silent overwrites.

Instructions

Creates a custom preset that inherits from a system preset, in the BambuStudio user profile directory; it appears in the dropdown after Bambu Studio is restarted. BambuStudio has no plugin API (see bambulab/BambuStudio#9614), so this is the only way to get parameters tuned by an AI into the GUI. Writes a file; an existing preset with the same name is never silently overwritten.

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": {
      "name": "<name>",
      "kind": "<kind>",
      "inherits": "<inherits>",
      "overrides": "<overrides>"
    },
    "name": "bambu_save_user_preset"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
nameYesName of the new preset; it appears in the Bambu Studio dropdown.
inheritsYesName of the system (vendor) preset to inherit from.
overridesYesParameters to override; each key is a BambuStudio setting name (e.g. layer_height, sparse_infill_density).
overwriteNoWhether to replace an existing preset with the same name. Defaults to false.

Output Schema

NameRequiredDescriptionDefault
pathYes
createdYes
nextStepYes
warningsYes
overwrittenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Adds real behavior beyond the annotations: it writes a file into the user profile directory, the result only shows up after a Bambu Studio restart, and an existing preset is never silently overwritten. Annotations already cover the safety profile (readOnly=false, destructive=false, non-idempotent), and the description is consistent with them; it stops short of describing what happens when 'inherits' names a preset that does not exist.

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?

Three sentences, front-loaded with what the tool does, then the why, then the safety guarantee. No filler, and the non-overwrite guarantee is placed last where it is most likely to be read as a caveat.

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?

An output schema exists, so return values need not be described, and the description covers the write location, inheritance model, and restart caveat. The only gap is that the three preset kinds (machine/process/filament) are left to the enum without any hint about how inheritance differs between them.

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 80%, so the schema already explains name, inherits, overrides, and overwrite. The description reinforces inheritance and dropdown visibility but adds no syntax, format, or constraint detail for the nested 'overrides' keys or the kind enum, so it lands at the baseline.

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 ("Creates a custom preset") plus the key mechanism ("inherits from a system preset, in the BambuStudio user profile directory"). This clearly separates it from read-side siblings like bambu_list_presets and bambu_resolve_preset, which do not write files.

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?

Gives a strong rationale for when to reach for it — "the only way to get parameters tuned by an AI into the GUI" because BambuStudio has no plugin API. It does not explicitly name the sibling tools an agent should use first (e.g. bambu_resolve_preset to validate the inherited preset), so the routing is implied rather than stated.

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