Skip to main content
Glama

PDF Sign API - add a typed or image signature and date

pdf_sign
Read-onlyIdempotent

Place a signature on a PDF: typed name in a handwriting-style font or your signature image (send it as a second file). Page, corner, size and date line selectable. Visual signature, not a certificate-based one. Runs on our server, files are deleted right after the call, nothing stored. Free: 25 calls/day per IP. Paid: $0.01 per call via x402 at https://radarbg.com/x402/pdf-sign.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "fileName": "sample.pdf",
      "signName": "Anna Petrova",
      "fileContent": "JVBERi0xLjMKJenr8b8KMSAwIG9iago8PAovQ291bnQgMQovS2lkcyBbMyAwIFJdCi9NZWRpYUJveCBbMCAwIDU5NS4yOCA4NDEuODldCi9UeXBlIC9QYWdlcwo+PgplbmRvYmoKMiAwIG9iago8PAovT3BlbkFjdGlvbiBbMyAwIFIgL0ZpdEggbnVsbF0KL1BhZ2VMYXlvdXQgL09uZUNvbHVtbgovUGFnZXMgMSAwIFIKL1R5cGUgL0NhdGFsb2cKPj4KZW5kb2JqCjMgMCBvYmoKPDwKL0NvbnRlbnRzIDQgMCBSCi9QYXJlbnQgMSAwIFIKL1Jlc291cmNlcyA2IDAgUgovVHlwZSAvUGFnZQo+PgplbmRvYmoKNCAwIG9iago8PAovRmlsdGVyIC9GbGF0ZURlY29kZQovTGVuZ3RoIDExMgo+PgpzdHJlYW0KeJwzUvDiMtAzNVco53IKUdB3M1QwNNIzMFAISVNwDQEJGRvqGVoomFua6pmbK4SkKGh45pXlZyanKhgZGJnpGhgYKrhWJOYW5KQq+JSkaCqEZKHqMzPXMzEC6wvJL0nMAZpuADLeNTQIphYAsdgfAQplbmRzdHJlYW0KZW5kb2JqCjUgMCBvYmoKPDwKL0Jhc2VGb250IC9IZWx2ZXRpY2EKL0VuY29kaW5nIC9XaW5BbnNpRW5jb2RpbmcKL1N1YnR5cGUgL1R5cGUxCi9UeXBlIC9Gb250Cj4+CmVuZG9iago2IDAgb2JqCjw8Ci9Gb250IDw8L0YxIDUgMCBSPj4KL1Byb2NTZXQgWy9QREYgL1RleHQgL0ltYWdlQiAvSW1hZ2VDIC9JbWFnZUldCj4+CmVuZG9iago3IDAgb2JqCjw8Ci9DcmVhdGlvbkRhdGUgKEQ6MjAyNjExMTUyMDEzNTRaKQo+PgplbmRvYmoKeHJlZgowIDgKMDAwMDAwMDAwMCA2NTUzNSBmIAowMDAwMDAwMDE1IDAwMDAwIG4gCjAwMDAwMDAxMDIgMDAwMDAgbiAKMDAwMDAwMDIwNSAwMDAwMCBuIAowMDAwMDAwMjg1IDAwMDAwIG4gCjAwMDAwMDA0NjkgMDAwMDAgbiAKMDAwMDAwMDU2NiAwMDAwMCBuIAowMDAwMDAwNjUzIDAwMDAwIG4gCnRyYWlsZXIKPDwKL1NpemUgOAovUm9vdCAyIDAgUgovSW5mbyA3IDAgUgovSUQgWzwyMzc0NENDOUY1ODJDN0FCMkFGMjQ5MDVFRTQ3RjgzNz48MjM3NDRDQzlGNTgyQzdBQjJBRjI0OTA1RUU0N0Y4Mzc+XQo+PgpzdGFydHhyZWYKNzA4CiUlRU9GCg=="
    },
    "name": "pdf_sign"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNolast, first, all or numlast
sizeNos, m or lm
filesNoOr several files: [{fileName, fileContent (base64)}]
styleNoserif, sans or boldserif
addDateNoAdd today's date under the signature
fileNameNoFile name with extension, e.g. report.pdf
positionNobr, bl, bc, tr or tlbr
signNameNoName to type as the signature (used when no signature image is sent)
pageNumberNoPage number when page=num
fileContentNoThe file as base64 (a data: URI is fine)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / pageNumber / minimum
      Added value: +1
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Although annotations already cover safety (readOnly, idempotent, openWorld), the description adds information annotations cannot express: server-side execution, immediate file deletion with nothing stored, the free 25 calls/day per IP cap, and the $0.01 x402 paid path. It also pre-empts a likely agent misconception by stating the signature is visual, not certificate-based.

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?

Three dense, front-loaded sentences with no filler: capability first, then the critical visual-not-certificate caveat, then operational facts. The pricing URL consumes meaningful space but carries decision-relevant information, so it earns its place.

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 10-parameter stateless signing tool with no output schema, the definition covers inputs, limits, cost, and data handling well. The one real gap is that it never says what comes back (presumably the signed PDF as base64 or a link), which matters for an agent planning the next step after the call.

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?

Schema coverage is 100%, so the baseline is 3, and the description earns above that by tying parameters to intent: it clarifies that the signature image travels as a second file (the files array) and that page, corner, size, and the date line are all selectable. It does not spell out page=num vs. last/first/all or the corner abbreviations, leaving those to the enum descriptions.

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?

"Place a signature on a PDF" gives a specific verb plus resource, then immediately names the two input modes (typed name in a handwriting-style font vs. a signature image sent as a second file) and the scope (visual signature, not certificate-based). An agent can distinguish this from siblings like pdf_watermark or pdf_flatten without opening the 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?

The description makes the typed-vs-image choice explicit and sets expectations about which mode applies when (signName is used when no signature image is sent). It stops short of naming any alternative tool or saying when NOT to use this one, so it is clear context rather than full routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources