qidi-mcp

bed_mesh_calibrate

Destructive

Probe the print bed to generate a new active mesh for accurate leveling. Save it afterward with a mesh profile, as calibration is not written to disk.

Instructions

Probe the bed and build a new mesh. Takes several minutes on the Max4's 9x9 grid and moves the toolhead across the whole bed; the bed should be at printing temperature for a meaningful result. The mesh is active immediately but NOT saved to disk — use bed_mesh_profile to save it. Two-step confirmation.

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

Input Schema

Name	Required	Description	Default
`confirm`	No
`profile`	No
`adaptive`	No
`confirm_token`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.1Nov 9, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations already flag this as destructive and non-idempotent, and the description adds substantial context on top: several minutes of runtime, full-bed toolhead motion, a temperature prerequisite, the fact that the mesh is live but not persisted, and that confirmation is two-step. Those are exactly the operational facts an agent needs before triggering an irreversible multi-minute action.

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?

Three short sentences, front-loaded with the action, then cost/preconditions, then the persistence caveat and confirmation requirement. No filler and nothing buried.

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 destructive, multi-minute calibration tool with an output schema covering returns, the description covers duration, physical side effects, prerequisites, persistence, and confirmation. The remaining gap is the unexplained profile and adaptive parameters, which materially affect how the tool is invoked.

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 four parameters, so the description must carry the burden. "Two-step confirmation" hints at confirm/confirm_token but never explains the sequence or what a confirm_token is, and neither profile nor adaptive is mentioned at all, leaving half the parameters undocumented anywhere.

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?

"Probe the bed and build a new mesh" gives a specific verb pair and resource, and the description explicitly contrasts itself with bed_mesh_profile (which persists the mesh). An agent can distinguish this from bed_mesh_profile and get_bed_mesh without opening any schema.

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 states the key precondition (bed at printing temperature for a meaningful result) and routes the agent to bed_mesh_profile to save the result. It does not differentiate this from adjacent leveling siblings like z_tilt_adjust, screws_tilt_calculate, or qidi_bed_level_calibrate, so the alternative-selection guidance is incomplete.

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

Deploy Server