Skip to main content
Glama

Get print job

get_print_job
Read-only

Retrieve a print job by ID with its line items, status, costs, shipping address, and tracking to monitor order progress and verify fulfillment.

Instructions

Get one Print-Job with its line items, status, costs, shipping address and tracking.

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": {
      "id": "<id>"
    },
    "name": "get_print_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPrint-Job id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds value by enumerating the returned content — line items, status, costs, shipping address and tracking — which matters because there is no output schema. It says nothing about behavior when the id is unknown or about auth/rate limits, keeping it below a 5.

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?

A single front-loaded sentence with the verb and resource first and the returned fields following; nothing is padded or redundant. It is on the terse side, but every clause contributes information.

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 simple one-parameter read with annotations covering the safety profile and no output schema, the description gives enough: what is fetched, by what identifier, and what comes back. Only edge-case behavior (missing job, whether costs are live or cached) is absent.

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?

There is a single parameter with 100% schema description coverage ('Print-Job id.' plus a pattern), so the schema already carries the semantics. The description only implies that a single job id is supplied and adds no format, sourcing, or lookup guidance beyond that.

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 verb and resource ('Get one Print-Job') and enumerates the payload it returns, so an agent knows this is a single-job detail fetch rather than a list. It does not name a sibling to contrast with, so the distinction from get_print_job_costs or get_print_job_status must be inferred from those names alone.

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?

'Get one Print-Job' implies a singular lookup by id, which is adequate context for a straightforward read. However, there is no explicit when-to-use or when-not guidance and no mention of when a narrower sibling (costs, status, statistics) would be preferable.

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