Skip to main content
Glama
ljbred08

percollate-mcp

by ljbred08
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

percollate_download_pdf

Download web pages as a formatted PDF. Bundle multiple URLs into one document with cover page, table of contents, and custom styling.

Instructions

Download one or more web pages as a beautifully formatted PDF file. Supports bundling multiple URLs into a single document with cover page and ToC.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cssNoAdditional CSS to override styles.
tocNoGenerate a table of contents.
urlsYesOne or more URLs to convert.
waitNoSeconds to wait between processing URLs (sequential mode).
coverNoGenerate a cover page.
debugNoPrint detailed debug info.
styleNoPath to a custom CSS stylesheet.
titleNoTitle for the bundle.
authorNoAuthor for the bundle.
inlineNoEmbed images inline as base64 data URLs.
no_ampNoDon't prefer the AMP version of the page.
outputNoOutput file path (absolute or relative). If it ends with / or has no extension, treated as a directory and a filename is auto-generated. Directories are created automatically.
templateNoPath to a custom HTML template (nunjucks). Applies to pdf, html, md.
hyphenateNoEnable hyphenation. Default: true for pdf, false otherwise.
toc_levelNoHeading depth for ToC (1–6). Values >1 imply --toc.
individualNoExport each URL as a separate file instead of bundling.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.7

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It implies downloading and file creation but does not disclose side effects, output file behavior, network/auth requirements, error handling, or rate/sequential-processing implications despite the tool writing a file to disk.

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 two front-loaded sentences with no wasted text. The core operation comes first, and the second sentence efficiently adds the bundling/cover/ToC capability.

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?

This is a complex tool with 16 parameters, no annotations, and no output schema. The description omits important invocation context such as output path behavior, individual vs bundled mode, and what the tool returns or writes, leaving too much to the schema alone.

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 description coverage is 100%, so the schema already documents all 16 parameters. The description only mentions bundling, cover page, and ToC, which overlaps with existing schema descriptions and adds no new syntax or meaning beyond them.

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 description states a specific verb and resource: 'Download one or more web pages as a ... PDF file.' It clearly distinguishes the PDF output format from the epub/html/md siblings, though it does not explicitly name those alternatives or spell out when to choose PDF over them.

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 explicit when-to-use guidance, no conditions for selecting this tool over the sibling format tools (epub, html, md), and no prerequisites or exclusions. The description merely states a capability rather than routing the agent among alternatives.

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

Deploy Server

Other Tools