preesy

Set print only

set_print_only

Idempotent

Turn print-only on or off for a Preesy session. With print-only on, the files can be printed but not downloaded, which keeps documents safer on shared computers. Use the manage_token of that session from its create_print_session result earlier in the conversation. The manage_token is secret. 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>",
      "print_only": "<print_only>"
    },
    "name": "set_print_only"
  }
}

Input Schema

Name	Required	Description	Default
`print_only`	Yes	true turns print-only on (print, no download). false turns it off so the file can be downloaded.
`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

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 1, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare the mutation and idempotency profile, and the description adds value beyond them: what print-only actually restricts (no download), the safety rationale for shared computers, and that an expired session returns status only. It stops short of stating permission requirements or the full return payload, but the useful behavioral context is there.

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?

Four short sentences, front-loaded with the action and effect before the token instructions. Slight duplication of 'print, no download' already in the schema prevents a perfect score, but nothing is wasted.

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?

With annotations covering safety and an output schema covering return values, the remaining need is the token source and edge-case behavior, both supplied (manage_token from create_print_session, expired sessions return status only). Complete enough 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?

Schema coverage is 100%, so both parameters are already fully documented, including the true/false meaning of print_only. The description reinforces the token's provenance and secrecy but adds little semantics the schema does not already contain, so baseline 3 applies.

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 ('Turn print-only on or off for a Preesy session') and immediately explains the concrete effect (print but not download). An agent can distinguish this from create_print_session, get_print_session and expire_print_session without opening any schema.

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 clear context for invocation: use the manage_token from the create_print_session result earlier in the conversation. It does not explicitly rule out alternatives, but the sibling set is create/get/expire and this is the only toggle, so ambiguity is low.

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?