Skip to main content
Glama

fulfillment_reprint_job

Resets a print job to pending so the agent prints it again; returns an error for unknown job IDs.

Instructions

Reset a print job to pending so the agent prints it again. Returns { ok: true }; 404 { ok: false, error } for an unknown job.

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": {
      "site": "<site>",
      "job_id": "<job_id>"
    },
    "name": "fulfillment_reprint_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesSite id (see list_sites)
job_idYesThe print job id (from fulfillment_queue)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.14.0
    • changedInput schema / properties / job_id / type
      Previous value: -"number"New value: +"integer"
  2. Addedv3.4.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose the state mutation (reset to pending) and both success and 404 response shapes, which is genuinely useful. It omits idempotency (what happens if the job is already pending), whether progress/history is discarded, and any auth or rate constraints on this write operation.

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 with the action and effect front-loaded, followed by return behavior. No filler or redundant restatement of the tool name.

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 two-parameter mutation with no output schema, the description covers the effect and the return contract, which is most of what an agent needs. It stops short of covering edge cases like idempotency or state preconditions on an unannotated write operation.

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 both site and job_id are already documented in the schema, including cross-references to list_sites and fulfillment_queue. The description adds no parameter-level meaning beyond that, so the baseline of 3 applies.

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 gives a specific verb and resource ('Reset a print job to pending') plus the intent ('so the agent prints it again'), which makes the operation unambiguous. It does not explicitly distinguish itself from siblings like fulfillment_queue, but none of the listed siblings appear to overlap, so confusion risk is low.

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?

Usage is implied by 'so the agent prints it again' — the condition for calling is that a job needs reprinting. There is no explicit when-not guidance, no mention of prerequisites such as job state or required permissions, and no named alternative for other queue operations.

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