Skip to main content
Glama
Sign In
Slicewise

Slicewise

by gjlmotea
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Compare two presets

bambu_compare_presets
Read-onlyIdempotent

Compares two Bambu Studio presets of the same kind, flattens them, and lists every differing setting so you can spot exact configuration changes without reading nested JSON.

Instructions

Flattens two presets of the same kind and lists the settings that differ. Use it to answer questions like "what exactly is the difference between 0.20 Standard and 0.20 Strength" without reading four levels of JSON by hand. No side effects.

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": {
      "left": "<left>",
      "right": "<right>",
      "kind": "<kind>"
    },
    "name": "bambu_compare_presets"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
leftYes
limitNo
rightYes

Output Schema

NameRequiredDescriptionDefault
leftYes
rightYes
differencesYes
differenceCountYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/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 "No side effects" adds nothing new. The one genuinely useful disclosure beyond annotations is "flattens", which tells the agent that inheritance chains are resolved — but it never mentions that a `limit` exists and can truncate the diff, which is the behavior an agent most needs to know.

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?

Three tight sentences with the core behavior front-loaded and the example placed as supporting evidence. The closing "No side effects" duplicates the annotation block and is the only sentence that doesn't earn its place.

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?

The existence of an output schema relieves the description of explaining return values, and the comparison semantics are clear. However, for a 4-parameter, 0%-coverage tool, the missing explanation of identifiers and of truncation via `limit` leaves a real gap an agent could trip on.

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

Parameters2/5

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

Schema description coverage is 0% and all four parameters are undescribed. The description only implies that `left`/`right` are preset identifiers and that `kind` must match, but says nothing about identifier format or the role of `limit` (max 500), leaving the caller to guess whether results can be silently cut off.

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?

"Flattens two presets of the same kind and lists the settings that differ" names a specific verb (compare/flatten), the resource (presets), and the output shape (differing settings). This is clearly distinguishable from bambu_list_presets and bambu_resolve_preset, which enumerate or resolve rather than diff.

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?

It gives a concrete motivating question ("what exactly is the difference between 0.20 Standard and 0.20 Strength") and states the precondition that both presets must be the same kind. It stops short of naming a contrasting sibling or explicitly saying when not to use 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