Apdf — PDF Tracking & Analytics

Underlay PDF Pages

underlay-pdf-pages

Underlay another PDF beneath pages of a base PDF (e.g. for backgrounds behind content).

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": "<file>",
      "underlay": "<underlay>"
    },
    "name": "underlay-pdf-pages"
  }
}

Input Schema

Name	Required	Description
`to`	No	Page-range expression in the underlay PDF to take from.
`file`	Yes	Publicly reachable URL of the base PDF file.
`from`	No	Page-range expression in the base PDF to underlay onto.
`async`	No	Run the action asynchronously and return a job id instead of the result. Poll "check-job-status" or set "webhook_url" to receive a callback.
`repeat`	No	Page-range expression of underlay pages to repeat.
`underlay`	Yes	Publicly reachable URL of the PDF to underlay underneath.
`webhook_url`	No	Callback URL invoked when an async job finishes. Only used when "async" is true.

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 28, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare destructiveHint=false. The description does not elaborate on behavioral traits such as async processing, return type, or file size limits. It adequately states the operation but adds no extra context beyond annotations.

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 is a single, well-constructed sentence that is front-loaded with the core action and purpose. No redundant or extraneous text.

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

Completeness2/5

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

Despite 100% schema coverage, the tool has 7 parameters including complex page-range expressions and async options. With no output schema, the description should explain what the tool returns (e.g., the modified PDF) and clarify page-range syntax or async behavior, which it does not.

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

Parameters3/5

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

Schema coverage is 100% with clear parameter descriptions. The tool description does not add meaningful information beyond what the schema already provides, so baseline score of 3 applies.

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 description clearly states the tool's function: underlaying one PDF beneath another, with a concrete example (backgrounds). This is specific and distinguishes from siblings like overlay-pdf-pages.

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 description gives a generic use case (backgrounds) but does not explicitly state when to use this tool versus alternatives like overlay-pdf-pages or merge-pdf-files. No exclusions or comparative guidance provided.

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

All Apdf — PDF Tracking & Analytics tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?