Skip to main content
Glama

get_history_totals

Read-onlyIdempotent

Retrieve lifetime QIDI printer totals for completed jobs, total print time, longest job, and filament used to track usage and maintenance needs.

Instructions

Lifetime totals for the machine: jobs completed, total print time, longest job, and total filament used.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A3.7/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 content of the totals but says nothing about scope caveats an agent might care about, such as whether the counters ever reset or whether totals are derived from retained history only. For a zero-parameter read this is adequate but not rich.

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?

A single front-loaded sentence that leads with the core concept ('Lifetime totals for the machine') and then lists the metrics. Every clause carries information; there is no filler or repetition of structured fields.

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?

With no parameters, a full output schema, and readOnly/idempotent annotations, the necessary description surface is small, and the sentence covers what the tool returns. The only gap is the absence of any note about the data's provenance or time boundary behind 'lifetime', which would help an agent interpret the numbers.

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 takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description does not waste effort restating an empty schema, which is correct.

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 description names the resource ('lifetime totals for the machine') and enumerates the four metrics returned: jobs completed, total print time, longest job, and total filament used. That makes the aggregate nature clear against per-job tools like get_print_history, though it never names that sibling 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?

The word 'lifetime' and the enumerated aggregates imply the right context (long-term statistics rather than current status), but there is no explicit 'use this instead of get_print_history when...' routing or any statement of when not to use it. An agent must infer the boundary from the wording alone.

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

Deploy Server

Other Tools