Tailprint

manage_pdf_lifecycle

Check, revoke, or extend the expiration of a Time-Limited Isotope PDF by document or file ID for real-time access control via status checks, a remote kill switch, or validity extensions.

Instructions

Manages the real-time lifecycle of a Time-Limited Isotope PDF document by doc_id or file_id: check expiration status ("status"), immediately revoke/expire the document via remote SCRAM Kill Switch ("expire_now"), or extend its validity window ("extend").

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

Input Schema

Name	Required	Description	Default
`action`	No	Lifecycle action: "status", "expire_now" (remote kill switch), or "extend"	status
`doc_id`	No	Document ID (e.g. doc_a94f82c1e0b319a4)
`file_id`	No	Hosted File ID (e.g. f_3b8e9a12c4d5e6f7.pdf)
`extend_by`	No	Duration to extend by when action="extend" (e.g. "24h", "7d", "14d")
`expire_message`	No	Optional custom expiration reason/message

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.4.0Nov 13, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations, the description carries the full burden, and it does disclose the most important behavioral fact: expire_now is an "immediate" remote "SCRAM Kill Switch" revocation, which tells the agent this branch is destructive and irreversible. It also flags the tool as operating in "real-time". It stops short of stating permission/auth requirements, whether extension is capped, or whether expiry can be undone.

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?

It is a single, front-loaded sentence that wastes no words, and the three action tokens are quoted so they can be matched against the enum. The nested parenthetical grouping of key-plus-action makes it slightly dense to scan, but nothing is padding.

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

Completeness3/5

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

For a 5-parameter, zero-required tool with no annotations and no output schema, the definition omits what the "status" branch actually returns (state, expiry timestamp, time remaining) and whether doc_id and file_id are mutually exclusive or interchangeable. The destructive branch is covered well; the read branch is not.

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 description coverage is 100%, so the schema already documents action, doc_id, file_id, extend_by and expire_message, including format examples such as "24h", "7d". The description adds no syntax, format, or constraint information beyond what the schema provides, so the 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?

The description names a specific verb+resource ("Manages the real-time lifecycle of a Time-Limited Isotope PDF document") and enumerates all three concrete actions with their quoted enum values. It also states the addressing keys (doc_id or file_id), which makes it trivially distinguishable from the sibling set of manipulation tools (compress, render, split, merge, stamp).

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?

Usage is implied through the three named actions rather than stated as conditions — an agent can infer that "status" checks, "expire_now" kills, and "extend" prolongs. However, there is no guidance on when to prefer this over alternatives, no statement that expire_now should only be used for confirmed revocation, and no guidance on choosing doc_id versus file_id. Baseline-adequate but with real gaps.

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

Deploy Server