Cloudlabels

List print stations

list_print_stations

Read-onlyIdempotent

Requires print. List Print Stations for this organization. Read only. Does not print and does not send a job. Each station has id, name, online, and last_seen_at. online is true when the last heartbeat is under 45 seconds old. printers is id, name, is_default, and paper. paper is name, width_mm, height_mm, and source. source printer_media is the roll a Brother printer reported: width_mm is the tape width, height_mm is the die-cut length, and height_mm is 0 for continuous tape. source windows_driver_form is the form the Windows driver has selected, used when the printer did not report a roll. paper is null when the station has not reported a form, and when a Brother printer reports that no tape is loaded. printers is an empty list when the station has not reported printers. Does not return pairing codes, tokens, or other secrets. Does not accept an organization id. print_labels still returns a PDF. Direct print is separate, and only when print_to_station and get_station_print_job are also in the tools list.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 30, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description still adds non-obvious behavior: the tool is implicitly scoped to the caller's organization, it never returns pairing codes or tokens, and 'online' is defined operationally as a heartbeat under 45 seconds — none of which is derivable from the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and the negative constraints are correctly front-loaded, but the body becomes an unstructured dense paragraph, and the paper/source explanation is repetitive ('height_mm is the die-cut length, and height_mm is 0 for continuous tape'). Most of the length is justified because no output schema exists, but it would read far better as structured bullets.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no parameters, the description carries the entire burden of explaining the response, and it does so thoroughly: station fields, the semantics of 'online', the nested printer/paper shape, both paper sources, and the null/empty-list cases. An agent can interpret every returned field without further documentation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are zero parameters, so the baseline is 4. The description reinforces this by explicitly stating it does not accept an organization id, which preempts an agent from inventing a scope argument despite the empty schema.

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?

States a specific verb and resource ('List Print Stations for this organization') and immediately rules out the adjacent operations ('Does not print and does not send a job'), which separates it cleanly from print_to_station, get_station_print_job, and print_labels in the sibling list.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives real routing guidance: 'print_labels still returns a PDF. Direct print is separate, and only when print_to_station and get_station_print_job are also in the tools list,' plus 'Requires print' as a precondition and 'Does not accept an organization id' as a scoping rule. It stops short of an explicit 'call this first to obtain station ids before print_to_station,' so it is clear context rather than a full when/when-not decision rule.

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

All Cloudlabels tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?