Fatia MCP

Overview Schema Source Related Servers Discussions Admin

create_calibration_project

Create unsliced Bambu Studio calibration projects and a manifest for explicit flow ratios, nozzle temperatures, or retraction lengths, using a compatible single-filament 3MF baseline.

Instructions

Create separate unsliced Bambu Studio calibration projects and a manifest for explicit flow ratios, fixed nozzle temperatures, or retraction lengths. Uses a compatible single-filament project as the settings baseline; replaces its geometry with closed test coupons. Temperature values require the baseline filament temperature range. Does not slice, run a heater, evaluate a physical result or change a preset.

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": {
      "path": "<path>",
      "kind": "<kind>",
      "values": "<values>"
    },
    "name": "create_calibration_project"
  }
}

Input Schema

Name	Required	Description
`kind`	Yes	Flow ratio uses a flat top-surface coupon; temperature uses a bridge coupon; retraction uses two posts on a shared base.
`path`	Yes	Existing single-filament 3MF whose settings already match the selected machine.
`values`	Yes	Explicit candidate values: flow ratio 0.8–1.2; temperature integer Celsius within the baseline filament range and known machine limit; retraction 0–2 mm. No values are guessed.
`bambu_model`	No	Printer model; falls back to BAMBU_MODEL or asks.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.1.47Nov 5, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations at all, the description carries the full burden and does substantial work: it discloses that output is unsliced, that a baseline project supplies settings, that geometry is replaced with closed coupons, that temperature values depend on the baseline filament range, that values are never guessed, and that it falls back to BAMBU_MODEL or asks. Gaps remain on filesystem effects (where projects are written, whether existing files are overwritten) which matter for a write-side tool.

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, front-loaded with the deliverable before the mechanics and constraints. No filler, though the final negation run-on packs four distinct exclusions that could read more cleanly as a list.

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 a 4-parameter write tool with no annotations and no output schema, the description supplies purpose, inputs' provenance, constraints, and explicit non-goals. What is missing is the observable result — where artifacts land and what the manifest contains — which an agent would need to chain into a later slicing step.

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 it by explaining that the baseline project must be a compatible single-filament file whose settings already match the machine, and that temperature candidates are constrained by the baseline filament's range. The 12-item cap on values and the manifest output are not elaborated, but the enum semantics are already covered in the schema.

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?

The description opens with a specific verb and resource ('Create separate unsliced Bambu Studio calibration projects and a manifest') and scopes it to three calibration types matching the kind enum. It implicitly separates itself from slicing/evaluation tools via explicit negations, but never names the nearest sibling (create_fit_test, slice_stl) so an agent must still infer the boundary.

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?

Usage context is clear: use it for explicit flow ratios, fixed nozzle temperatures, or retraction lengths driven by a compatible baseline project. The closing sentence gives strong when-not conditions ('Does not slice, run a heater, evaluate a physical result or change a preset'), though it stops short of naming which sibling to use for those steps.

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