preesy

Get print session

get_print_session

Read-onlyIdempotent

Check a Preesy print session's status with its manage_token. Use the manage_token of that session from its create_print_session result earlier in the conversation. The manage_token is a secret and must be kept private. one_time_access: If true, this is a single-use label. As soon as a file or the zip is printed or downloaded, it is removed from the system. one_time_used: True once a file or the zip has been printed or downloaded. The label is then removed from the system. An expired session returns status only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "manage_token": "<manage_token>"
    },
    "name": "get_print_session"
  }
}

Input Schema

Name	Required	Description	Default
`manage_token`	Yes	Secret returned by create_print_session. Keep it private. A label and PIN do not work here.

Output Schema

Name	Required	Description
`label`	No
`status`	Yes
`expires_at`	No	Expiry time in RFC3339 UTC.
`print_only`	No
`one_time_used`	No	True once a file or the zip has been printed or downloaded. The label is then removed from the system.
`one_time_access`	No	If true, this is a single-use label. As soon as a file or the zip is printed or downloaded, it is removed from the system.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 1, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the bar is lower; the description still adds real context beyond them — the token is a secret that must stay private, one-time labels are removed once printed or downloaded, and an expired session returns status only. That last point about expiry behavior is not 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.

Conciseness4/5

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

Purpose and token sourcing are front-loaded, then the flag semantics. The one_time_access/one_time_used sentences are slightly dense and field-oriented, but each carries distinct meaning and nothing is redundant.

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

Completeness4/5

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

A single-parameter read tool with an output schema and full annotation coverage; the description supplies the operational caveats an agent needs (secret handling, expiry, one-time label removal). No important gap remains for correct invocation.

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

Parameters3/5

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

Only one parameter and the schema covers it at 100%, including the note that a label and PIN do not work here. The description reinforces the secrecy requirement but adds no syntax or format detail beyond the schema, so baseline 3 applies.

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?

States a specific verb and resource ("Check a Preesy print session's status") and ties the input to its origin tool, so it is distinguishable from create_print_session and expire_print_session. It stops short of explicitly contrasting with the siblings.

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?

It says where the manage_token comes from ("from its create_print_session result earlier in the conversation"), which implies the natural call sequence, but gives no explicit when-to-use/when-not-to-use versus expire_print_session or set_print_only.

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

All preesy 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?