Skip to main content
Glama

Count print jobs by status

get_print_job_statistics
Read-only

Count print jobs by status, optionally filtered by date, status, or ID, to monitor production and order progress.

Instructions

Count Print-Jobs in each status, optionally filtered by date, status or id.

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

Input Schema

NameRequiredDescriptionDefault
idNoFilter by Print-Job id.
pageNoResult page, default 1.
statusNoFilter by status: CREATED, REJECTED, UNPAID, PAYMENT_IN_PROGRESS, PRODUCTION_READY, PRODUCTION_DELAYED, IN_PRODUCTION, ERROR, SHIPPED or CANCELED.
orderingNoField to sort by.
page_sizeNoResults per page, default 100.
created_afterNoOnly items created after this ISO 8601 date or timestamp (UTC), e.g. '2026-11-09' or '2026-11-09T09:30:08Z'.
created_beforeNoOnly items created before this ISO 8601 date or timestamp (UTC), e.g. '2026-11-09' or '2026-11-09T09:30:08Z'.
modified_afterNoOnly items modified after this ISO 8601 date or timestamp (UTC), e.g. '2026-11-09' or '2026-11-09T09:30:08Z'.
modified_beforeNoOnly items modified before this ISO 8601 date or timestamp (UTC), e.g. '2026-11-09' or '2026-11-09T09:30:08Z'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

The readOnlyHint and openWorldHint annotations already establish the safety profile, and the description adds that results are counts per status with optional filtering. It does not disclose pagination behavior, ordering effects, or the exact response structure, so it adds only moderate behavioral context beyond the 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?

The definition is a single front-loaded sentence that states the core operation and optional filters without unnecessary wording. Every clause contributes directly to selecting and invoking the tool.

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?

For a read-only aggregation tool with nine optional parameters and full schema coverage, the description is largely complete: it identifies the aggregate output and the available filter categories. It could still say more about how this differs from list_print_jobs, but nothing essential for 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 description coverage is 100%, so every parameter is already documented in the input schema. The description mentions date, status, and id filtering, but does not add syntax or meaning beyond the schema and omits mention of ordering and pagination parameters. Baseline 3 applies when the schema does the heavy lifting.

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 uses the specific verb “Count” with the resource “Print-Jobs” and states the grouping dimension “in each status.” This clearly distinguishes an aggregate statistics tool from sibling tools such as list_print_jobs and get_print_job.

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 phrase “optionally filtered by date, status or id” implies useful filtering contexts, but it gives no explicit when-to-use guidance, exclusions, or comparison with sibling tools. The agent must infer that this should be chosen over list_print_jobs when only aggregate counts are needed.

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