FreeDailyPro Tools

pdf_compress_lossless_bw

Read-onlyIdempotent

Shrink a scanned PDF from freedailypro by turning pages into pure black-and-white JBIG2 pictures, each page coded exactly as read (no letter is ever swapped; safe for contracts and numbers). Colour and shading are lost and text on converted pages is no longer selectable. A page is converted only when that makes it at least 10% smaller; other pages (for example real-text pages) are copied untouched. Errors if the PDF is unreadable, password-protected, over 100 pages, or if no smaller file results.

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_lossless_bw"
  }
}

Input Schema

Name	Required	Description	Default
`dpi`	No	Render resolution, 100 to 200. Default 150
`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

A3.9/5.0

Behavior5/5

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

The description goes well beyond the annotations by disclosing what is lost (colour, shading, selectable text), the 10%-smaller gate that keeps untouched pages intact, and concrete limits (unreadable, password-protected, >100 pages, no size gain). These are exactly the behavioral facts an agent needs before committing a document.

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?

Sentences are front-loaded and dense with operational facts; nothing is filler. It is on the longer side, but the length is justified by the safety caveats it must convey.

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

Completeness4/5

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

With no output schema, the description should say what comes back; it hints at 'if no smaller file results' but never states the return shape (e.g. base64 PDF payload). It is otherwise complete for a two-parameter conversion tool.

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 fileBase64 and the 100-200 dpi range are already documented in the schema. The description reinforces limits (100 pages) but adds no dpi semantics, so the baseline 3 applies.

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 names a specific verb (shrink), resource (scanned PDF), and technique (JBIG2 black-and-white, bit-exact lossless page coding). It implicitly separates itself from the other pdf_compress_* siblings by emphasizing 'lossless' and 'no letter is ever swapped', but it never explicitly names which sibling to use instead.

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?

It provides strong situational cues ('safe for contracts and numbers') and lists failure conditions, but gives no explicit routing guidance between this tool and the many sibling compressors (pdf_compress_smallest_bw, pdf_compress_greyscale, pdf_compress_balanced, etc.). The agent must infer when this specific variant beats the alternatives.

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

All FreeDailyPro 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?