qidi-mcp

download_file

Read-onlyIdempotent

Read printer files as text from gcodes, config, or logs roots, truncating output to a byte budget and optionally tailing the end to avoid flooding context.

Instructions

Read a file off the printer as text (truncated to a byte budget so it cannot flood context). Works on any root: 'gcodes' for prints, 'config' for printer.cfg and friends, 'logs' for klippy.log. Use tail=true to read the end.

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": {
      "path": "<path>"
    },
    "name": "download_file"
  }
}

Input Schema

Name	Required	Default
`path`	Yes
`root`	No	config
`tail`	No
`max_bytes`	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/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds non-obvious behavior beyond that: output is truncated to a byte budget specifically so it cannot flood context, which is valuable for an agent sizing its call.

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 tight sentences with no filler; the core purpose and the truncation safeguard are front-loaded, followed by the root values and the tail hint in a logical order.

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 described, and the description covers roots, truncation, and tail adequately for a 4-parameter read tool. The only omission is any explanation of the required 'path' parameter, which is fairly self-evident.

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 the description must carry parameter meaning. It documents the meaningful enum-like values for 'root' and the purpose of 'tail', and implies max_bytes via 'byte budget', but never names max_bytes or explains 'path' semantics, leaving a real gap.

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 ('Read a file off the printer as text') and adds a scope detail (truncated to a byte budget). It implicitly separates itself from metadata, copy, and delete siblings through the word 'Read' and 'as text', but never explicitly names an alternative.

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 selection guidance for the 'root' parameter ('gcodes' for prints, 'config' for printer.cfg, 'logs' for klippy.log) and when to set tail=true. It lacks any explicit exclusions or pointers to sibling tools for other file operations, so it falls short of a full 5.

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

Deploy Server