qidi-mcp

get_system_info

Read-onlyIdempotent

Check host and service health—Moonraker/Klipper versions, OS/CPU load, memory, uptime, undervoltage flags, and MCU errors—to diagnose odd print failures.

Instructions

Host and service health: Moonraker/Klipper versions, the printer's OS and CPU, load, memory, uptime, throttle flags (undervoltage), MCU load and communication error counters. Use this when prints fail oddly — an undervoltage flag or MCU bandwidth saturation explains a lot.

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

Input Schema

Name	Required	Description	Default
No arguments

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/5.0

Behavior4/5

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

The annotations already establish that this is a read-only, idempotent, non-destructive operation, so the description does not need to restate safety. It adds useful behavioral context by framing the output as diagnostic evidence for odd print failures, including undervoltage and MCU saturation, which helps an agent understand why to call it.

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?

The description is two tight sentences with the resource and diagnostic fields front-loaded, followed by the key usage scenario. Every clause contributes either selection or interpretation value, with no filler.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given a zero-parameter, read-only diagnostic tool with an output schema, the description is complete enough for selection and invocation. It explains what system-level data is returned and why an agent would want it, while the output schema can carry the detailed return shape.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so there is no parameter semantics to clarify and the baseline is 4. The description does not need to explain any input formats or constraints.

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?

The description names the exact resource and scope: host and service health for Moonraker/Klipper versions, OS/CPU, load, memory, uptime, throttle flags, MCU load, and communication error counters. An agent can distinguish this from siblings like get_printer_status or get_temperatures because it is explicitly about system-level diagnostics rather than live print state or temperatures.

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?

It gives a clear triggering scenario: use when prints fail oddly, especially because undervoltage or MCU bandwidth saturation can explain failures. It does not mention when not to use it or name specific alternative diagnostic tools, so it falls short of full when/when-not guidance.

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

Deploy Server