Skip to main content
Glama
Sign In
Tailprint

Tailprint

by coheroseb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

verify_pdf

Detects tampering in Tailprint PDFs by validating the HMAC-SHA256 signature and visual fingerprint, then extracts the embedded Dual-Brain JSON without OCR.

Instructions

Verifies the cryptographic HMAC-SHA256 signature and visual content fingerprint of a Tailprint PDF to detect tampering, and extracts its embedded Dual-Brain structured JSON payload in 0ms without OCR.

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": {
      "pdf": "<pdf>"
    },
    "name": "verify_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
pdfYesPDF document as a base64 string, base64 data URI, or public HTTP/HTTPS URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden. It does disclose real behavior — HMAC-SHA256 verification, fingerprint comparison, 0ms/no-OCR extraction — but never states what happens on a failed verification (exception vs. a negative result), whether the call is purely read-only, or any input constraints on the source PDF beyond the schema.

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

Conciseness5/5

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

A single dense sentence that front-loads the verification action and then the extraction capability; every clause carries information and nothing is repeated from the name or schema.

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?

For a one-parameter verification tool with no output schema, the description covers both the verification outcome domain (tamper detection) and the returned payload, which is most of what an agent needs. The remaining gap is the shape of a verification failure, which is not described anywhere.

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 is only one parameter and schema coverage is 100%, so the schema already documents the accepted forms (base64, data URI, public URL). The description adds no further syntax or size/format constraints beyond that, which is acceptable at the single-parameter baseline of 4.

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?

Names a specific verb (verifies) plus the exact resources it acts on — the HMAC-SHA256 signature and visual content fingerprint of a Tailprint PDF — and adds a second distinct capability (extracting the embedded Dual-Brain JSON). This is clearly distinguishable from the sibling PDF tools such as compress_pdf, split_pdf, or render_pdf, which manipulate rather than verify.

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?

The phrase 'of a Tailprint PDF' implicitly scopes usage to documents produced by this system, which is useful, but there is no explicit when-to-use statement, no comparison to any alternative, and no stated preconditions. Usage is inferable but not guided.

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

Deploy Server

Other Tools