Find Printix printers and print queues in your tenant. Filter by search query and page through results.
List Printix print queues/printers for the tenant, optionally filtered by search query and paged.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Zero-based page number. | |
| query | No | Optional free-text search filter. | |
| pageSize | No | Results per page. |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Since no annotations are provided, the description carries the burden of behavioral disclosure. It does convey that this is a read-style listing operation with optional filtering and paging, but it does not explain query matching behavior, default page size, result shape, or any tenant-scoping caveats.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, well-structured sentence that front-loads the main purpose and then mentions the optional filter and pagination. There is no redundant or unnecessary content.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple list operation with fully documented optional parameters, the description provides adequate context. However, with no output schema, it would benefit from mentioning what fields or objects are returned, and from noting pagination defaults such as page size behavior.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already documents all three parameters. The description adds only that query is a search filter and the result is paged, which is minimal but acceptable given the schema already provides per-parameter details.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states a specific action ('List'), a specific resource ('Printix print queues/printers'), and a scope ('for the tenant'). It also distinguishes itself from sibling tools like printix_get_printer, which retrieves a single printer rather than listing all of them.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description clearly indicates this is the tool for listing printers tenant-wide, with optional query filtering and pagination. It does not explicitly mention printix_get_printer as the alternative for retrieving a single printer, so it lacks an explicit exclusion, but the listing context is clear enough.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.