Skip to main content
Glama

Apdf — PDF Tracking & Analytics

by io.apdf
OverviewAdmin

Overlay PDF Pages

overlay-pdf-pages

Overlay another PDF on top of pages of a base PDF (e.g. for watermarks above content).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoPage-range expression in the overlay PDF to take from.
fileYesPublicly reachable URL of the base PDF file.
fromNoPage-range expression in the base PDF to overlay onto.
asyncNoRun the action asynchronously and return a job id instead of the result. Poll "check-job-status" or set "webhook_url" to receive a callback.
repeatNoPage-range expression of overlay pages to repeat.
overlayYesPublicly reachable URL of the PDF to overlay on top.
webhook_urlNoCallback URL invoked when an async job finishes. Only used when "async" is true.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  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 provide destructiveHint=false. Description adds minimal behavioral details beyond 'overlay on top'. No mention of file creation, authorization, or side effects.

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?

Single sentence of 16 words, front-loaded with action and example. No wasted words.

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?

No output schema, but parameters cover async behavior in schema. Description lacks details on return value, output format, or completion semantics. Adequate but not complete.

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%, so parameters are already documented. Description adds no additional parameter meaning beyond the example hint. Baseline 3 is appropriate.

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 action (overlay), resource (PDF pages), and a common use case (watermarks). It distinguishes from siblings like merge-pdf-files and underlay-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 implies usage with the watermark example but does not explicitly state when to use or not use this tool versus alternatives. Sibling tools are listed but no differentiation.

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 toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources