Skip to main content
Glama
Sign In
qidi-mcp

qidi-mcp

by couplet-physical-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

move_file

Move or rename a file or directory on a QIDI printer by specifying source and destination paths that include the root.

Instructions

Move or rename a file/directory on the printer. Both paths include the root, e.g. source='gcodes/old.gcode', dest='gcodes/archive/new.gcode'. Requires confirm=true.

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": {
      "source": "<source>",
      "dest": "<dest>"
    },
    "name": "move_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
destYes
sourceYes
confirmNo
confirm_tokenNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A3.7/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false and destructiveHint=false; the description adds the useful precondition that confirmation is required, which the annotations do not convey. However it is silent on whether dest overwrites an existing file, whether the source is removed atomically, and how confirm_token participates in confirmation, so the mutation's real risk profile stays opaque.

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 followed by the path-format example and the confirmation requirement. No filler, though the 'confirm=true' clause could have been fused with the path guidance more economically.

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 not be explained, and the path-format example covers the main agent pitfall (missing root). The remaining gap is confirm_token, an undocumented non-required parameter in a four-parameter mutation tool.

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%, yet the description does compensate partially: it gives concrete path examples with the root included for source and dest and names the confirm flag. The fourth parameter, confirm_token, is never mentioned, leaving an agent with no idea of its type semantics or how it relates to confirm.

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 pair and resource: "Move or rename a file/directory on the printer." The rename case expands the scope beyond what the name 'move_file' implies, and the effect is immediately graspable relative to siblings like copy_file and delete_file.

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?

The description is implicitly about file management and states the confirm=true precondition, but it never says when to pick this over copy_file (move vs copy semantics) or when a rename should instead be handled differently. No exclusions or alternatives are named.

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