qidi-mcp

set_speed_factor

Adjust the live print speed override as a percentage (10–200) to slow a running print and fix quality problems without stopping the job.

Instructions

Set the print speed override (M220) as a percentage, 10–200. Applies live to a running print. Slowing a print that is having quality trouble is a common fix.

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": {
      "percent": "<percent>"
    },
    "name": "set_speed_factor"
  }
}

Input Schema

Name	Required	Description	Default
`confirm`	No
`percent`	Yes
`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

B3.3/5.0

Behavior3/5

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

Annotations already declare it is a non-read-only, non-idempotent, non-destructive mutation, and the description adds genuinely useful context: the change applies live to a running print. It says nothing about the confirm/confirm_token path, whether the override persists past the job, or whether values are clamped versus rejected out of range — meaningful gaps for a live mutation.

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 operation and its constraints, with no filler. The usage hint is compact and placed after the specification rather than before it.

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 core action is fully specified. But for a live mutation gated by a confirm token, the absence of any explanation of the confirmation mechanics or persistence behavior leaves the agent guessing on a nontrivial part of the call.

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%, so the description must carry the load. It usefully supplies the 10–200 bounds for 'percent' (not in the schema), but the confirm and confirm_token parameters — which imply some confirmation gate — are never mentioned, leaving two of three parameters with no semantics anywhere.

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 ('Set the print speed override') and pins it down with the M220 G-code reference plus the 10–200 range, which distinguishes it from nearby siblings like set_flow_factor (M221) and set_fan_speed. It stops short of naming an alternative explicitly, so it is clear but not fully sibling-differentiated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Slowing a print that is having quality trouble is a common fix' provides a real usage context rather than nothing. However, there are no exclusions, no prerequisites, and no routing guidance versus set_flow_factor, which is the obvious confusable alternative for quality problems.

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

Deploy Server