Skip to main content
Glama
ipp-bridge-mcp

ipp-bridge-mcp

List Jobs

list_jobs
Read-only

Retrieve active or completed print jobs from an IPP printer or CUPS queue to monitor status and track print activity.

Instructions

List active or completed print jobs on the IPP printer or CUPS queue.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
backendNoauto
which_jobsNonot-completed
printer_uriNo
printer_nameNo

Output Schema

NameRequiredDescriptionDefault
resultYes

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?

readOnlyHint=true already establishes that this is a safe read with no side effects, so the description has a lower bar to clear. It adds the useful scope detail that results span both active and completed jobs and can come from either an IPP printer or a CUPS queue, matching the backend parameter. It says nothing about ordering, pagination behavior, or how many jobs are returned when limit is not set, so the added context is modest.

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?

A single front-loaded sentence with the verb first and the scope qualifiers immediately after. Nothing is redundant and nothing needs trimming.

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

Completeness3/5

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

An output schema exists, so the description is not obligated to describe return values, and the read-only annotation covers safety. However, with five optional parameters at zero schema coverage and real complexity in target selection (backend auto/ipp/lp, printer_uri vs printer_name), the definition leaves meaningful decisions undocumented.

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 five parameters, so the description should carry the explanatory load, and it does not. Only the job-state notion is loosely echoed by 'active or completed'; limit, backend, printer_uri, printer_name, and the enum values of which_jobs go entirely unexplained, including the crucial distinction between identifying a queue by URI versus by name.

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 ('List ... print jobs') plus the source systems (IPP printer or CUPS queue) and the job-state scope ('active or completed'). It is clearly distinct from siblings like list_printers or cancel_job, though it never explicitly names a differentiating sibling such as get_job_status.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance: nothing says to prefer this over get_job_status for a single job, or when to use it before cancel_job. The reader must infer the intended workflow entirely from the name and the 'active or completed' phrasing.

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