Skip to main content
Glama

Подписать PDF текстом

sign_pdf

Ставит одну текстовую подпись (например, «Иванов И. И.») в заданное место одной страницы PDF — самый простой способ подписать. Рукописная подпись картинкой, несколько подписей или подпись вместе с текстом и пометками — edit_pdf (объект signature). Это изображение подписи, не электронная подпись (не КЭП). file_url: публичный URL PDF-файла. signature_text: текст подписи. page: номер страницы (с 1). x, y: координаты (0.0–1.0). width, height: размер блока (0.0–1.0).

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": {
      "file_url": "<file_url>",
      "signature_text": "<signature_text>"
    },
    "name": "sign_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNo
yNo
pageNo
widthNo
heightNo
file_urlYes
signature_textYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Beyond the annotations, it discloses the one-signature/one-page limit, the public-URL requirement, and the crucial fact that the result is a signature image rather than a cryptographic or qualified electronic signature. It does not add rendering details such as font or appearance behavior, but the disclosed traits are directly relevant to correct selection and invocation.

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?

The description front-loads purpose, alternatives, and the important signature-type caveat, then uses compact parameter lines. Every sentence adds selection, behavioral, or invocation information without repeating schema defaults or otherwise padding the text.

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?

Together with the schema defaults and output schema, this provides nearly everything needed to select and invoke the tool correctly, including its main prerequisite and limitations. The principal remaining gap is the coordinate reference frame and anchor, which matters for the tool's core placement task.

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?

With 0% schema description coverage, the description usefully documents all seven inputs: public URL, signature text, 1-based page numbering, normalized coordinates, and normalized block dimensions. It leaves the coordinate origin and whether x/y denote the block's corner or another anchor unspecified, so precise placement still requires inference.

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 opening sentence specifies the action, resource, and exact scope: placing one text signature at a chosen location on one PDF page. It also distinguishes the tool from edit_pdf for handwritten-image, multiple, or mixed-content signatures.

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

Usage Guidelines5/5

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

It identifies this as the simplest option for a single text signature and explicitly routes handwritten-image, multiple-signature, and text-plus-annotation scenarios to edit_pdf. The warning that it is not a qualified electronic signature further prevents selecting it for cryptographic signing.

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.