Skip to main content
Glama
ipp-bridge-mcp

ipp-bridge-mcp

Validate Print Job

validate_print_job
Read-only

Check a document and job options against a printer without printing, confirming settings are valid before submitting a real print job.

Instructions

Validate an uploaded file_id or local_path against the printer without printing.

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

Input Schema

NameRequiredDescriptionDefault
mediaNo
sidesNo
copiesNo
backendNoauto
file_idNo
job_nameNo
number_upNo
color_modeNo
local_pathNo
orientationNo
page_rangesNo
printer_uriNo
media_sourceNo
printer_nameNo
print_qualityNo
document_formatNo
requesting_user_nameNo
ipp_attribute_fidelityNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is non-mutating, and the description usefully reinforces that nothing is printed. Beyond that it discloses nothing about the validation itself - no mention of what is checked, whether it contacts the printer versus only validating locally, or backend behavior - though the output schema absorbs the return-value burden.

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 front-loaded sentence with no wasted words. It is efficient, though arguably undersized for a tool with 18 parameters and no schema documentation.

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?

With 18 optional parameters, 0% schema coverage, and no required fields, the definition leaves the agent guessing which parameters matter for a validation call and what combination is valid. The output schema covers results, but input-side completeness is inadequate for this complexity.

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 18 parameters, and the description only mentions two of them (file_id, local_path). Print-critical options like media, sides, copies, page_ranges, printer_name/printer_uri, backend, and ipp_attribute_fidelity carry no meaning anywhere, so the description does not compensate for the coverage gap.

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?

Names a specific verb (validate), names the exact inputs (file_id or local_path), and states the scope 'against the printer without printing', which cleanly separates it from print_file and other siblings.

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?

'Without printing' implicitly positions this as a pre-flight check before print_file, but no alternative is named and there is no explicit when-to-use/when-not guidance. It also fails to state that at least one of file_id or local_path must be supplied, which matters since required parameters are zero.

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