Skip to main content
Glama

Водяной знак

watermark_pdf

Добавляет водяной знак на страницы PDF. file_url: публичный URL PDF-файла. text: текст водяного знака (исключает image_url). image_url: URL PNG-изображения для водяного знака (исключает text). opacity: прозрачность 0.0–1.0 (по умолчанию 0.3). angle: угол поворота текста (по умолчанию 45). position: center | tile | top-left | top-right | bottom-left | bottom-right.

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>"
    },
    "name": "watermark_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNo
angleNo
opacityNo
file_urlYes
positionNocenter
image_urlNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnly=false, destructive=false, openWorld=true, and non-idempotent, so the safety profile is largely supplied. The description adds that file_url must be a public URL and that text/image_url are mutually exclusive, plus defaults and ranges, but does not say whether the original PDF is modified or how output is delivered.

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 purpose is front-loaded, followed by compact parameter lines. Every sentence maps to a parameter and adds useful constraints without repetition or filler.

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?

Given annotations and an output schema, the description covers purpose and all parameter semantics adequately. However, it omits tool-selection guidance versus siblings and does not explicitly state that at least one of text or image_url should be supplied, which is a meaningful gap because only file_url is required.

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

Parameters5/5

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

With 0% schema description coverage, the description defines every one of the six parameters: public PDF URL, watermark text, PNG image URL, opacity 0.0–1.0 with default 0.3, angle default 45, and position values center/tile/top-left/top-right/bottom-left/bottom-right. It also states mutual exclusivity between text and image_url, adding meaning absent from the bare schema.

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 first sentence names a specific verb and resource: adding a watermark to PDF pages. It is clearly distinct from most sibling conversion tools, though it does not explicitly contrast with add_page_numbers, the closest sibling.

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 when-to-use or when-not-to-use guidance, and no alternative tool is named. Usage is only implied by the tool name and parameter list, without explaining when text versus image_url should be chosen beyond their mutual exclusivity.

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.