Skip to main content
Glama

Нумерация страниц

add_page_numbers

Добавляет номера страниц в PDF. file_url: публичный URL PDF-файла. position: bottom-center | bottom-right | top-center | top-right. start_from: стартовый номер (по умолчанию 1). prefix: текст перед номером, например "Стр. " или "— ". font_size: размер шрифта 6–72 (по умолчанию 12).

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": "add_page_numbers"
  }
}

Input Schema

NameRequiredDescriptionDefault
prefixNo
file_urlYes
positionNobottom-center
font_sizeNo
start_fromNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, but the description adds no behavioral context beyond them. It does not say whether a new file is produced or the source is modified, what happens on a URL fetch failure, or any size/page limits — notable for a network-touching mutation tool.

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?

One lead sentence followed by a per-parameter list — front-loaded and free of filler. The list form is efficient, though it consumes the whole definition and leaves no room for contextual guidance.

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

Completeness3/5

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

An output schema exists, so return values need not be explained, and the parameters are well covered. For an open-world mutation tool with five parameters, though, the absence of any note on output file handling or failure modes leaves a real gap.

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 description coverage is 0%, so the description carries the full burden, and it does document all five parameters: the public URL, the allowed position values, the start number default, prefix examples, and the 6–72 font-size range. Only file_url lacks constraint detail (e.g., size or accessibility requirements).

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 opening line states a specific verb and resource ("Добавляет номера страниц в PDF"), which unambiguously distinguishes it from pitch-related siblings like watermark_pdf. It does not, however, name which sibling to use instead when the user actually wants a stamp or watermark, so differentiation is implicit rather than explicit.

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?

The description never says when to choose this over watermark_pdf, edit_pdf, or reorder_pages, and gives no prerequisites such as the file needing to be publicly reachable. Usage is only inferable from the tool name and the parameter list.

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.