Skip to main content
Glama
ljbred08

percollate-mcp

by ljbred08
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

percollate_download_html

Download web pages as a self-contained HTML file using Percollate. Embed images as base64, add a table of contents, cover page, or custom CSS for offline reading.

Instructions

Download one or more web pages as a self-contained HTML file. Use the 'inline' option to embed images as base64.

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?

With no annotations, the description carries the full behavioral burden, and it discloses little. 'Self-contained HTML file' hints at output form, but it doesn't say the file is written to disk, where it lands, whether processing is sequential or parallel, or what happens with multiple URLs. These are material behaviors an agent must know before invoking.

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?

Two sentences, front-loaded with the core action, no padding. The second sentence is borderline redundant against the schema, which keeps it just short of a 5.

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 16-parameter tool with no annotations and no output schema, and the description addresses only the required 'urls' concept and one boolean. Bundling vs 'individual' export, the directory-vs-file semantics of 'output', and the parent/child CLI context are all left unexplained by the description.

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% across all 16 parameters, so the baseline is 3. The description's note about the 'inline' option merely restates the schema's own text ('Embed images inline as base64 data URLs') and adds no new syntax, defaults, or interactions for the other 15 parameters.

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 gives a clear verb and resource — download web pages as a self-contained HTML file — and the 'HTML' qualifier implicitly separates it from the pdf/epub/md siblings. It doesn't explicitly name or contrast those alternatives, but the format-specific naming makes the distinction readable.

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?

No guidance on when to choose HTML over the pdf, epub, or md siblings, and no mention of prerequisites (network access, sequential vs individual mode). The only usage hint is about the 'inline' option, which is an option, not a selection criterion.

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