Skip to main content
Glama
ipp-bridge-mcp

ipp-bridge-mcp

Print File

print_file

Send a staged document to an IPP/IPPS printer or CUPS queue by file ID or local path, with controls for copies, media, sides, color, and page ranges.

Instructions

Print a staged file (by file_id or local_path) directly via IPP or CUPS lp.

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

Input Schema

NameRequiredDescriptionDefault
mediaNo
sidesNo
copiesNo
backendNoauto
dry_runNo
file_idNo
job_nameNo
number_upNo
color_modeNo
local_pathNo
orientationNo
page_rangesNo
printer_uriNo
media_sourceNo
printer_nameNo
print_qualityNo
validate_firstNo
document_formatNo
cleanup_after_printNo
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

C2.9/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden. It discloses the backend mechanism (IPP vs CUPS lp) but says nothing about side effects: that cleanup_after_print can delete the staged file, that validate_first defaults to true and may reject the job, or that dry_run performs no printing. These are material behaviors an agent must know before invoking a 21-parameter mutation.

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 filler, and the key input alternatives appear before the backend detail. It is efficient, though arguably too terse for a tool with this many knobs.

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?

An output schema exists, so return values need not be described. But with 21 parameters, zero schema coverage, and no annotations, the description leaves the agent without the operational context needed to call this safely, particularly around validation and file cleanup.

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 21 parameters, and the description documents only the file_id/local_path alternative and the backend choice. Critical parameters like dry_run, validate_first, cleanup_after_print, page_ranges, and printer_uri vs printer_name receive no explanation, leaving most of the surface undocumented in both schema and description.

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 gives a specific verb (print) and resource (a staged file), and names the two acceptable input modes, file_id or local_path. It does not explicitly distinguish itself from siblings such as validate_print_job, so it stops short of a 5.

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?

The phrase 'staged file' implies a prior upload_file step, and naming file_id vs local_path gives an either/or hint. However, there is no explicit guidance on when to call validate_print_job first, when to use dry_run, or what to do if no printer is specified.

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