BambuStudio-MCP

Overview Schema Source Related Servers Discussions Admin

start_slice

Queue a detached BambuStudio slice for a project or selected plate, then poll the job for results. Run geometry analysis first to surface warnings before slicing.

Instructions

Queue a detached Studio slice. Run analyze_geometry first and show its highlighted preview. Unresolved or missing geometry analysis returns warnings, not a block. Poll get_job. 0 selects all plates; positive indexes are 1-based.

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": {
      "project_id": "<project_id>"
    },
    "name": "start_slice"
  }
}

Input Schema

Name	Required	Description	Default
`revision`	No
`project_id`	Yes
`plate_index`	No
`timeout_seconds`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 19, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already establish that this is a non-read-only, non-destructive, closed-world mutation. The description goes beyond them by disclosing the asynchronous queuing model, that missing geometry analysis produces warnings rather than an error, and that completion must be polled via get_job. It does not mention the timeout or what a returned job handle looks like.

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?

Four short sentences, each carrying distinct information: action, prerequisite, failure semantics, follow-up, plus parameter semantics. Front-loaded with the operation and no filler.

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?

For an async job-launch tool with no output schema, the description supplies the workflow, the failure mode, and the polling requirement, which is most of what an agent needs. The unexplained revision and timeout_seconds parameters are the only remaining gap.

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 0%, so the description carries the burden and does explain the most confusing parameter: plate_index, where 0 selects all plates and positive values are 1-based. However, revision and timeout_seconds receive no explanation, so compensation is only partial for a four-parameter tool.

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?

Uses a specific verb ("Queue") plus a precise resource ("detached Studio slice"), which distinguishes it from siblings such as inspect_slice and analyze_geometry. It stops short of explicitly contrasting with the nearest sibling (inspect_slice), but the action is unambiguous.

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?

Gives an explicit prerequisite (run analyze_geometry first and show its highlighted preview), the failure behavior (unresolved geometry yields warnings, not a block), and the follow-up (poll get_job). That is a complete when/how sequence an agent can act on directly.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.