Skip to main content
Glama

pdf_timestamp

Add RFC 3161 cryptographically verified TSA timestamp tokens to PDFs to prove when a document existed.

Instructions

Cryptographic Timestamp TSA: Apply RFC 3161 cryptographically verified TSA timestamp tokens. [Input: .pdf | Output: .pdf]

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": {
      "input": "<input>",
      "output": "<output>"
    },
    "name": "pdf_timestamp"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes
outputYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It implies an external network call to a TSA and modification of the document, but it does not say whether the input file is altered in place, whether a TSA URL or credentials are required, or whether failures occur when the TSA is unreachable.

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?

The definition is a single compact sentence with the operation front-loaded and format hints bracketed at the end. It is efficient, though the bracket notation is terser than it needs to be and adds little beyond the schema's string types.

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

Completeness2/5

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

For a tool with no annotations, no output schema, and 0% parameter documentation, the description is too thin. It omits the TSA dependency, error behavior, and path semantics, which an agent needs in order to invoke this tool reliably.

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

Parameters2/5

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

Schema description coverage is 0% for the two required parameters. The '[Input: .pdf | Output: .pdf]' tags hint that both are PDF file paths, but they do not clarify whether these are local paths, workspace references, or URLs, nor how the output is named.

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?

The description names a specific verb and resource: 'Apply RFC 3161 cryptographically verified TSA timestamp tokens.' That clearly distinguishes it from conversion and manipulation siblings such as html_to_pdf or pdf_compress. It does not explicitly contrast with any sibling, but the action is unambiguous.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus other PDF operations, and no prerequisites are stated. In particular, an RFC 3161 timestamp normally requires a TSA server endpoint or credentials, and nothing here tells the agent to supply or expect one.

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