Skip to main content
Glama
ipp-bridge-mcp

ipp-bridge-mcp

List Printers

list_printers
Read-only

Retrieves configured IPP printers and local CUPS destinations to identify available print targets for validation, printing, and job management.

Instructions

List configured IPP printers and/or local CUPS destinations.

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_printers"
  }
}

Input Schema

NameRequiredDescriptionDefault
backendNoauto

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes this is a safe read operation, so the description is not carrying the full safety burden. It adds useful context by clarifying that results span both IPP-configured printers and local CUPS destinations, but says nothing about ordering, empty results, or service-unavailable behavior — though an output schema exists to cover the return shape.

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 or redundancy. It is arguably too terse rather than too long, but it wastes no words and leads with the core action.

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?

The tool is simple (one optional enum parameter, output schema present), so the description needn't explain return values or pagination. However, the unexplained backend selector is a real gap for a tool whose entire behavior is choosing between two printer backends, leaving the definition only marginally sufficient.

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%, so the description must explain the single 'backend' parameter, and it does not. The enum values (auto, ipp, lp) are never mentioned or mapped to the 'IPP printers' vs 'local CUPS destinations' distinction, leaving the agent to guess which value selects which source and what 'auto' does.

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 ('List') and a specific resource ('configured IPP printers and/or local CUPS destinations'), making the scope of what is returned clear. It does not explicitly distinguish itself from siblings like get_printer_attributes or identify_printer, but the listing semantics are unambiguous on their own.

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 statement of prerequisites (e.g. that the CUPS service must be reachable), and no routing to alternatives such as get_printer_attributes for details on a single printer. An agent must infer that this is the discovery/entry-point tool from the word 'List' alone.

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