FreeDailyPro PDF Tools

pdf_compress_extreme

Read-onlyIdempotent

Shrink a PDF from freedailypro as far as it will go (the site's Extreme mode): everything Aggressive does, then every page as 70 dpi greyscale and as pure black-and-white JBIG2 (exact, then with shared letter shapes), keeping the smallest. Colour and shading are lost and text is no longer selectable; very rarely a letter in tiny print can be swapped for a look-alike one in the symbol-mode result, so check important numbers in the original. Heavy: several seconds per page; returns the best level finished so far (truncated: true) if the time budget runs out. Errors if the PDF is unreadable, password-protected, over 100 pages, or if nothing gets smaller.

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": {
      "fileBase64": "<fileBase64>"
    },
    "name": "pdf_compress_extreme"
  }
}

Input Schema

Name	Required	Description	Default
`fileBase64`	Yes	The PDF, base64 encoded (up to 20 MB, up to 100 pages)

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 28, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the read-only and idempotent annotations, the description discloses consequential behavior: colour and shading loss, loss of text selectability, rare letter substitution in symbol-mode output, several seconds per page runtime, truncated results when the time budget expires, and specific error conditions. This is unusually thorough behavioral disclosure.

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?

The description is front-loaded with the core action and mode, and every clause carries useful information about output quality, performance, truncation, or errors. It is dense and could be easier to scan with structure, but it avoids filler.

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

Completeness5/5

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

For a single-parameter tool with full schema coverage and existing safety annotations, the description covers the remaining agent-relevant details: quality tradeoffs, rare symbol-mode artifacts, performance expectations, truncation behavior, and error conditions. Nothing essential for correct invocation appears missing.

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?

There is only one parameter, fileBase64, and the schema already documents it at 100% coverage, including the 20 MB and 100-page limits. The description reinforces the 100-page limit through its error list but adds no new meaning about the parameter itself, so the baseline of 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 uses a specific verb and resource: 'Shrink a PDF' in the site's Extreme mode. It explicitly distinguishes this from its closest sibling by saying it does 'everything Aggressive does' plus additional greyscale and JBIG2 processing, so an agent can identify it without consulting other tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description makes the use case clear: maximum compression at the cost of colour, shading, and selectable text. It references the Aggressive mode as a baseline and lists heavy runtime and failure conditions, but it stops short of explicitly naming the preferred alternative for cases where colour or selectable text matters.

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

All FreeDailyPro PDF Tools tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?