qidi-mcp

move_relative

Jog the 3D printer toolhead by a relative dx/dy/dz offset in millimeters with bounds checking and policy limits; requires confirmation and is blocked during printing.

Instructions

Jog the toolhead by a relative offset in mm (any of dx/dy/dz). The destination is computed and bounds-checked before moving, and a single jog is capped by policy. 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_relative"
  }
}

Input Schema

Name	Required	Description	Default
`dx`	No
`dy`	No
`dz`	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.1/5.0

Behavior4/5

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

Annotations already declare the mutation profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), and the description adds real context beyond them: destination is computed and bounds-checked before motion, and a single jog is capped by policy. It does not say what happens on a bounds or policy violation (rejection vs clamping) or what happens to the confirm requirement.

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, front-loaded with what the tool does, followed by safety behavior and preconditions. No redundant restatement of the name or padding.

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

Completeness3/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 safety-critical behavior is covered. Against six parameters at 0% coverage and a motion operation, the missing feedrate semantics and the unexplained confirm_token leave an agent guessing on invocation details.

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 coverage is 0%, so the description must carry the load; it defines dx/dy/dz as relative offsets in mm and confirms that confirm=true is mandatory. However, feedrate (including whether units are mm/s or mm/min) and confirm_token are entirely undocumented in both schema and description, leaving two of six parameters opaque for a motion tool.

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?

States a specific verb and resource ("Jog the toolhead") plus the offset semantics ("relative offset in mm"), and the word "relative" cleanly separates it from the sibling move_absolute without needing to name it.

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 preconditions — requires confirm=true, blocked during a print — which tells the agent when the call will fail. It stops short of explicitly routing to an alternative (e.g. move_absolute for absolute coordinates), so it is strong context rather than a full when/when-not/alternative map.

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

Deploy Server