Skip to main content
Glama
ipp-bridge-mcp

ipp-bridge-mcp

Cancel Job

cancel_job
Destructive

Cancel a queued or active print job by job ID to stop unwanted output and free printer resources.

Instructions

Cancel a queued or active print job by job_id.

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

Input Schema

NameRequiredDescriptionDefault
job_idYes
backendNoauto
printer_uriNo
printer_nameNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

The destructiveHint=true annotation already signals this is an irreversible mutation, so the description is not obliged to re-state that. It does add useful scope (only queued or active jobs) but says nothing about what happens on failure, whether a backend or printer hint is needed to disambiguate job_ids, or any permission requirements.

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 tight sentence with the resource and key identifier front-loaded and no filler. It is efficient, though the brevity comes at the cost of the parameter guidance noted above.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The presence of an output schema means return values need no explanation, but for a destructive mutation with three undocumented optional parameters (including one enum), the description is too thin to guarantee correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 4 parameters, so the description must compensate and it does not: only job_id is mentioned. The backend enum (auto/ipp/lp) and the printer_uri/printer_name disambiguation fields are left entirely unexplained, which matters for correctly targeting a job.

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 uses a specific verb and resource ("Cancel a queued or active print job") and scopes it by job_id, so an agent can immediately tell it apart from read-oriented siblings like get_job_status or list_jobs. It stops short of explicitly naming an alternative, but the operation itself is unambiguous.

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 only implied: the phrase "queued or active" hints that already-completed or unknown jobs are not eligible, but there is no explicit when-to-use/when-not-to-use guidance and no mention of prerequisites such as verifying state first with get_job_status. The agent must infer the workflow.

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