Skip to main content
Glama
Sign In
Slicewise

Slicewise

by gjlmotea
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Explain parameters and their trade-offs

bambu_describe_parameters
Read-onlyIdempotent

Explains what a 3D printing parameter controls, its unit, range, trade-offs, and related settings before you change it, so you can tune presets by evidence instead of guesswork.

Instructions

Explains what a parameter does, its unit, its typical range, the cost of raising or lowering it, and related parameters. Call this before changing any parameter, instead of tuning by what merely sounds reasonable. No side effects.

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

Input Schema

NameRequiredDescriptionDefault
keysNo
groupNo

Output Schema

NameRequiredDescriptionDefault
specsYes
unknownYesKeys that are not in the parameter catalog.

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 readOnly, idempotent, non-destructive, and closed-world, so 'No side effects' merely restates the structured data. The description does add that responses carry cost/trade-off and related-parameter context, which is useful, but it says nothing about failure behavior for unknown keys, whether results are exhaustive, or how much detail to expect.

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?

Two front-loaded sentences that describe the payload then the usage rule; nothing extraneous. The closing 'No side effects' is slight waste since annotations already declare it.

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?

An output schema exists, so return structure needn't be explained, and the read-only annotations cover safety. What remains missing is any description of the two input parameters and their interaction, which for a 0%-coverage schema is the main thing an agent needs before calling it.

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% for two parameters, yet the description never mentions 'keys' or 'group' at all. It gives no hint whether keys are parameter names, whether group and keys can be combined, whether group overrides keys, or what happens when both are omitted — a significant gap the schema cannot fill on its own.

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?

The description states a specific verb and resource and enumerates exactly what the explanation covers: function, unit, typical range, cost of raising/lowering, and related parameters. It is clearly distinguishable from sibling tools like bambu_list_presets or bambu_optimize_print_in_place, which mutate or enumerate rather than explain.

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 an explicit trigger ('call this before changing any parameter') and rules out a bad alternative approach ('instead of tuning by what merely sounds reasonable'). It does not name a sibling tool it competes with or state when the tool is unnecessary, so it falls short of a 5.

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