Skip to main content
Glama
Sign In
qidi-mcp

qidi-mcp

by couplet-physical-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

save_z_offset

Destructive

Persist the current live Z offset via QIDI's M1002 routine so it survives a restart. Dial it in first, then confirm to write persistent printer state.

Instructions

Persist the current live Z offset using QIDI's M1002 routine, so it survives a restart. Use set_z_offset to dial it in first, then this to keep it. Two-step confirmation, because it writes persistent state.

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

Input Schema

NameRequiredDescriptionDefault
confirmNo
confirm_tokenNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and non-idempotent, and the description adds the key behavioral fact that this writes persistent state surviving a restart, plus that confirmation is a two-step process. It stops short of explaining how the confirm token is obtained or what happens if confirmation is skipped.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences, front-loaded with the action and rationale, with the sibling routing placed before the confirmation caveat. Every clause carries information; only the missing token detail keeps it from being ideal.

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?

A destructive, non-idempotent mutation tool whose persistence semantics and two-step confirmation are disclosed, and an output schema exists so return values need no explanation. The one notable omission is guidance on obtaining and passing confirm_token.

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 description coverage is 0%, so both parameters (confirm, confirm_token) rely on the description, which only alludes to 'two-step confirmation' without mapping it to the fields or describing token acquisition and expiry. It compensates partially but leaves real gaps.

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 ('Persist the current live Z offset'), names the underlying routine (QIDI M1002), and gives the outcome ('survives a restart'), which cleanly separates it from set_z_offset.

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

Usage Guidelines5/5

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

Explicitly sequences the workflow: 'Use set_z_offset to dial it in first, then this to keep it.' The alternative and the condition that selects it are both named, leaving nothing to inference.

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

Deploy Server

Other Tools