qidi-mcp

input_shaper_calibrate

Destructive

Run resonance testing with the toolhead accelerometer to calculate input shaper settings for a QIDI Max 4 printer.

Instructions

Run resonance testing with the toolhead accelerometer and compute optimal input shaper settings (SHAPER_CALIBRATE). The gantry is shaken hard through a frequency sweep — loud, and it must not be interrupted. Results are applied in memory; saving them rewrites printer.cfg. Two-step confirmation. Note: the Max4 also ships QIDI's own M901 macro for this.

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

Input Schema

Name	Required	Description	Default
`axis`	No
`confirm`	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/5.0

Behavior5/5

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

Annotations already mark this destructive and non-idempotent, and the description adds exactly the missing operational detail: the machine is shaken hard and is loud, interruption is unsafe, results live in memory only, and persisting them rewrites printer.cfg. The two-step confirmation requirement also explains the confirm/confirm_token behavior, which is not visible anywhere else.

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 tight sentences, front-loaded with what the tool does before the safety and persistence caveats. Every sentence carries non-redundant information, including the final alternative-path note.

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?

An output schema exists, so return values need no explanation, and the destructive/persistence/confirmation story is well covered. Gaps remain around preconditions for a mechanical shake test (idle state, homing) and the meaning of the axis parameter, which is the one call-shaping decision left to guesswork.

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 all three parameters. The description only obliquely accounts for confirm and confirm_token via 'Two-step confirmation', and says nothing about axis — its valid values (x/y or both) or the consequence of leaving it null for a full sweep.

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?

States a specific verb and resource ('run resonance testing with the toolhead accelerometer and compute optimal input shaper settings') and anchors it to the underlying macro SHAPER_CALIBRATE, so it is clearly not a plain settings write like set_input_shaper. It never names a sibling tool explicitly, so differentiation is inferential rather than stated.

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 operational context for use — do not interrupt, two-step confirmation, results are volatile until saved — and flags the firmware-side M901 macro as an alternative path on the Max4. It stops short of a selection rule (when to prefer M901 or set_input_shaper over this) or preconditions such as the printer needing to be idle or homed.

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

Deploy Server