Skip to main content
Glama
ipp-bridge-mcp

ipp-bridge-mcp

Get Job Status

get_job_status
Read-only

Retrieve attributes and current state for a specific print job ID, so you can track job progress and diagnose printing issues across IPP or CUPS backends.

Instructions

Get attributes and state for a specific print 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": "get_job_status"
  }
}

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

C2.6/5.0
Behavior2/5

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

readOnlyHint=true already declares the safety profile, and the output schema covers the return shape, so 'attributes and state' adds essentially nothing beyond the tool name. Nothing is said about what the backend selector changes, whether state is live or cached, or how errors for unknown job IDs behave.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

A single front-loaded sentence with zero filler, but it is under-sized for a tool with four parameters and three mutually exclusive backend modes. Brevity here costs information rather than saving it.

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 output schema means return values need no explanation, but the input side is bare: no coverage of backend selection or printer identification. For a four-parameter, three-backend tool, the description leaves too much for the agent to guess.

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 coverage is 0% across four parameters. The description only implies job_id; it says nothing about the backend enum (auto/ipp/lp), or about when printer_uri versus printer_name must be supplied, leaving half the surface undocumented in both schema and prose.

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 (Get) and resource (attributes and state for a print job), keyed by job ID. An agent can tell this apart from list_jobs or cancel_job from the name and sentence, though the description never names a sibling explicitly.

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, no prerequisites, and no mention of alternatives such as list_jobs for enumerating jobs. The agent must infer the retrieval context from the tool name alone.

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