Skip to main content
Glama
Sign In
Bambi A1 MCP

Bambi A1 MCP

by chandraaditya
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

prepare_job

Slices STL or 3MF files with Bambu Studio and creates snapshots of sliced 3MFs for inspection without printing. For STL, supply process and filament profiles; set slice:true for unsliced 3MF.

Instructions

Snapshot and inspect a sliced 3MF, or slice STL/3MF using Bambu Studio. Does not print. STL requires process and filament profile paths. Use slice:true for an unsliced 3MF.

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": {
      "file_path": "<file_path>"
    },
    "name": "prepare_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
sliceNo
file_pathYes
plate_indexNo
process_profileNo
filament_profilesNo
process_overridesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.7

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description must carry the full behavioral load; it does disclose the key non-action ('Does not print') and the STL prerequisites. However, it says nothing about side effects (whether a sliced artifact is written to disk), runtime cost of slicing, or what snapshot/inspect returns, which matters for a Bambu Studio-backed operation.

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 short sentences, front-loaded with the core capability and with the negative constraint placed early. Efficient, though the compression contributes to the parameter gaps rather than resolving them.

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

Completeness2/5

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

Six parameters, a nested object, no output schema, no annotations, and zero schema descriptions make this a high-burden definition. The description covers the file-type branching but omits plate selection, override semantics, and any sense of result or failure modes.

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% across six parameters, including a nested process_overrides object with wall_loops, layer_height, and sparse_infill_density. The description only hints at slice, process_profile, and filament_profiles, leaving plate_index and the entire overrides object undocumented anywhere.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names two concrete operations with specific resources: snapshotting/inspecting a sliced 3MF, and slicing STL/3MF via Bambu Studio. 'Does not print' cleanly separates it from print_job, though the dual-mode framing takes a moment to parse.

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 actionable conditions: STL requires process and filament profile paths, and slice:true is needed for an unsliced 3MF. It also implicitly routes printing to a sibling via 'Does not print', but never names get_job, verify_job, or print_job as the follow-on steps.

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