qidi-mcp

get_printer_config

Read-onlyIdempotent

Retrieve live Klipper configuration from Moonraker to inspect resolved settings or list section names; pass a section to read only that section and avoid the large full tree.

Instructions

The printer's live Klipper configuration as Moonraker reports it: either the resolved settings tree (section -> key -> value) or the list of section names. Pass a section name to get just that section — the full tree is large.

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_printer_config"
  }
}

Input Schema

Name	Required	Description	Default
`section`	No
`list_sections`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.1Nov 9, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds a real behavioral fact — that the unscoped result is large — but says nothing about how the live config relates to on-disk config, caching, or snapshot timing.

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 what is returned and followed by the scoping advice. No filler; could only be improved by naming the second parameter directly.

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?

For a two-parameter read-only tool with an output schema, this covers purpose, both output shapes and the size trade-off. Nothing essential to correct invocation is missing.

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 coverage is 0%, so the description carries the burden and does partially cover both parameters: 'section' is described as narrowing to one section. The list-of-section-names mode is mentioned as an output shape but never tied to the 'list_sections' boolean, leaving that parameter's role to inference.

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 resource (the printer's live Klipper configuration as Moonraker reports it) and the two shapes it can take (resolved settings tree vs. section name list). It is clearly distinct from status-oriented siblings like get_printer_status, though it never names an alternative explicitly.

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?

Offers one concrete usage cue — pass a section name when the full tree is too large — which is genuinely helpful. It does not explain when to use list_sections versus a section lookup, nor when to prefer this over query_objects or get_saved_variables.

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

Deploy Server