qidi-mcp

move_absolute

Moves the 3D printer toolhead to absolute X/Y/Z coordinates in millimeters, holds axes left unspecified, and requires confirmation; blocked during printing.

Instructions

Move the toolhead to absolute coordinates in mm. Supply any of x/y/z; omitted axes hold position. feedrate is mm/min (capped by policy). Axes must be homed and each coordinate must be inside the machine's travel. Requires confirm=true. Blocked during a print.

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

Input Schema

Name	Required	Description	Default
`x`	No
`y`	No
`z`	No
`confirm`	No
`feedrate`	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.4/5.0

Behavior5/5

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

Annotations only cover readOnly/idempotent/destructive flags; the description adds preconditions the agent could not otherwise know: homing requirement, travel-limit validation, mandatory confirm, print-state blocking, and a policy-capped feedrate. These are exactly the failure modes an agent needs before calling a motion command. Minor tension: 'absolute coordinates' reads as repeatable while idempotentHint is false, but that is not a direct contradiction.

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 (operation, partial-axis semantics, units, preconditions), with the core action front-loaded and no filler.

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

Completeness5/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 not be described. For a state-changing motion tool with six parameters, the description covers the operation, axis semantics, units, and every precondition needed to avoid a failed or unsafe call.

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 0%, so the description carries the burden, and it does for five of six parameters: omission semantics for x/y/z, units and capping for feedrate, and the confirm requirement. confirm_token is never explained, leaving the second half of the confirmation flow undocumented.

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 ('Move the toolhead') plus the coordinate mode ('absolute coordinates in mm'), which implicitly distinguishes it from move_relative. It stops short of naming the relative-move sibling explicitly, so the routing signal is inferred 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 concrete use conditions: any subset of x/y/z, omitted axes hold position, axes must be homed, coordinates must be inside travel, confirm=true required, and it is blocked during a print. That is a clear when/when-not set; the only gap is that no alternative tool is named for the relative-move or mid-print cases.

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

Deploy Server