Skip to main content
Glama

Cancel print job

cancel_print_job
DestructiveIdempotent

Cancels a print job before it enters production, including jobs that are created, unpaid, or production delayed. Use it to stop an order permanently; the action cannot be undone.

Instructions

Cancel a Print-Job. Only possible before it goes to production (statuses CREATED, UNPAID or PRODUCTION_DELAYED). This cannot be undone.

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": "cancel_print_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPrint-Job id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered structurally. The description adds genuinely new behavioral context: the status precondition (which implies a failure mode once the job reaches production) and the irreversibility warning. It does not explain what state the job ends in or what error surfaces when the status gate is violated, which keeps 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the action, then the constraint, then the irreversibility warning. Nothing is redundant or padded; every sentence carries a distinct fact.

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 one-parameter mutation tool with rich annotations and no output schema, the description covers the key decision inputs: eligibility and irreversibility. It leaves minor gaps about the resulting job state and the error behavior on ineligible jobs, but the essential information is present.

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 coverage is 100%, and the single `id` parameter is documented in the schema as "Print-Job id." with a pattern constraint. The description adds no extra meaning about the id (e.g., where to obtain it), so the baseline 3 applies.

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 gives a specific verb+resource ("Cancel a Print-Job") that is unambiguously distinct from siblings like get_print_job, create_print_job, and reprint_print_job. An agent can identify the operation without opening the schema.

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?

It states the precise eligibility condition (only before production, listing the exact statuses CREATED, UNPAID, PRODUCTION_DELAYED), which tells the agent both when to use it and when not to. It stops short of naming an alternative route for jobs past that stage, so it is clear but not fully explicit about alternatives.

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