Skip to main content
Glama
ipp-bridge-mcp

ipp-bridge-mcp

Get Printer Attributes

get_printer_attributes
Read-only

Retrieve detailed printer status, supported formats, media, and marker levels to validate print jobs and choose correct settings.

Instructions

Query detailed printer status, supported formats, media, and marker levels.

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

Input Schema

NameRequiredDescriptionDefault
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.9/5.0
Behavior3/5

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

The readOnlyHint=true annotation already tells the agent this is a non-mutating read, so the bar is lower. The description adds that the returned data is operational detail (marker levels imply consumable/toner readings), which is modest added context. It says nothing about failure behavior for unreachable printers, authentication needs, or fallback across backends.

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 well-formed sentence with no redundancy and the resource front-loaded. It is efficient, though its brevity is part of why the parameter and selection semantics are missing.

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 and readOnlyHint carry much of the load, but the tool has three entirely undocumented parameters and no target-selection rule for a call that needs to know which printer to query. The description does not close that gap.

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 three parameters, so the description must compensate and does not. It never explains the auto/ipp/lp backend choice, nor whether printer_uri and printer_name are alternatives or must agree, nor what happens when both are null despite neither being required.

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 ('Query') plus resource ('printer') and enumerates the payload: status, supported formats, media, and marker levels. That is far more informative than the bare name. It does not, however, distinguish itself from siblings such as identify_printer or list_printers, so an agent must infer that this is the deep-attribute read versus a discovery or identification call.

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 mention of prerequisites, and no routing to or away from related tools like identify_printer or list_printers. An agent gets the what but not the when.

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