qidi-mcp

get_print_history

Read-onlyIdempotent

Retrieve past 3D print jobs with status, duration, filament use, and timestamps to check whether the last print succeeded or identify failure patterns.

Instructions

Past print jobs with status, duration, filament used and timestamps. Useful for 'did the last print succeed?' and for spotting a pattern of failures.

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

Input Schema

Name	Required	Description	Default
`limit`	No
`start`	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.5/5.0

Behavior3/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 the shape of the returned data, but says nothing about ordering (newest-first?), how pagination behaves, or what happens when no history exists. Useful context, but not rich behavior beyond annotations.

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?

Two short sentences, zero filler, with the data content front-loaded before the motivating use cases. Every clause earns its place.

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

Completeness3/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 needn't be spelled out, and the description briefly characterizes them anyway. However, for a history/pagination tool, the absence of any guidance on paging through results or narrowing by recency leaves the agent under-equipped to call it correctly beyond the default page.

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

Parameters2/5

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

Schema description coverage is 0% — 'limit' and 'start' carry only bare titles and defaults. The description does not mention pagination at all, so the agent gets no explanation of what 'start' offsets or whether 'limit' caps results per page. This is the main gap in the definition.

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?

The first sentence names the specific resource (past print jobs) and enumerates the fields returned (status, duration, filament used, timestamps), which is enough to distinguish it from siblings like get_job_status or get_history_totals. It never explicitly names those siblings, so differentiation relies on the agent's inference.

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?

Two concrete use cases are given ('did the last print succeed?' and 'spotting a pattern of failures'), which tells the agent when this tool is appropriate. It stops short of exclusions or naming the aggregate/current-status alternatives, so routing between get_print_history, get_history_totals, and get_job_status is left to inference.

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

Deploy Server