qidi-mcp

get_file_metadata

Read-onlyIdempotent

Read slicer metadata from a G-code file to verify estimated time, filament requirements, temperatures, and settings before starting a print.

Instructions

Full slicer metadata for one G-code file: estimated time, filament length and weight, layer heights, per-object height, nozzle diameter, filament type, first-layer and chamber temperatures, thumbnails present, and the slicer used. Read this before start_print to confirm the file matches the loaded filament.

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": {
      "filename": "<filename>"
    },
    "name": "get_file_metadata"
  }
}

Input Schema

Name	Required	Description	Default
`filename`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.1Nov 9, 2026

TDQS

A4.1/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 genuine context beyond that: it is per-file, field-rich, and framed as a pre-print validation step. It does not say what happens when the filename is missing or invalid, which is the remaining gap.

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 sentences, front-loaded with purpose and followed by the workflow rationale. The long colon-delimited field list is dense but each item is informative; it is close to the upper bound of useful length but does not waste words.

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 no explanation, and the description covers purpose, contents, and a usage trigger. What remains thin is filename resolution semantics and error behavior, which matter for a file-addressed read.

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% for the single 'filename' parameter, so the description has to carry the burden. It implies the argument identifies one G-code file but never clarifies whether it is a bare name, a path relative to a file root, or an absolute path. Baseline 3 for a thin one-parameter schema.

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 ('Full slicer metadata for one G-code file') and enumerates exactly which fields are returned. The singular 'one G-code file' scopes it apart from list_gcode_files and list_directory without needing the schema.

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 an explicit workflow trigger: 'Read this before start_print to confirm the file matches the loaded filament.' That names both the moment to call it and the sibling it precedes. It stops short of when-not guidance or mentioning adjacent tools like check_print_fit that could plausibly overlap.

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

Deploy Server