Skip to main content
Glama
JohanRouyer

Bambu Studio Advisor

by JohanRouyer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Compare two presets

compare_presets
Read-onlyIdempotent

Compare two presets of the same type to see only settings whose values differ, with inheritance resolved. Use it to spot what a user preset changes from a Bambu preset or how two profiles differ.

Instructions

Compare two presets of the same type and return only the settings whose values differ (setting, value in A, value in B), inheritance resolved. Read-only. Use it to see what a user preset changes from a Bambu preset, or how two profiles differ; use get_preset to read one preset in full. Fails if either name is unknown.

Input Schema

NameRequiredDescriptionDefault
kindYesPreset type: "process" (print settings), "filament" or "machine" (printer).
preset_aYesExact name of the first preset.
preset_bYesExact name of the second preset, of the same type.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.0.1
    • addedInput schema / properties / kind / description
      Added value: +"Preset type: \"process\" (print settings), \"filament\" or \"machine\" (printer)."
    • addedInput schema / properties / preset_a / description
      Added value: +"Exact name of the first preset."
    • addedInput schema / properties / preset_b / description
      Added value: +"Exact name of the second preset, of the same type."
  2. First observedv1.0.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare read-only and idempotent, so the safety bar is low. The description adds valuable context: inheritance is resolved, only differing settings are returned, and unknown names cause failure. It does not describe pagination or limits, but the output schema exists.

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 tight sentences with the core behavior front-loaded, followed by usage guidance and a failure note. No wasted wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present and annotations covering safety, the description provides everything an agent needs: scope, return behavior, usage routing, and failure mode.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds meaning beyond the schema by enforcing that the two presets must be the same type and that unknown names cause failure, which shapes correct invocation.

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 (compare), resource (presets), scope (same type, only differing settings), and return shape (setting, value A, value B). Clearly distinct from get_preset, which is named as the read-one alternative.

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?

Explicitly names use cases (see what a user preset changes from a Bambu preset, how two profiles differ) and routes the agent to get_preset for full reads. Also states the failure condition when a name is unknown.

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