FreeDailyPro Tools

pdf_compress_greyscale

Read-onlyIdempotent

Shrink a scanned PDF from freedailypro by turning pages into 100 dpi greyscale JPEG pictures: shading and photos are kept, colour is dropped, text on converted pages is no longer selectable. Larger than the black-and-white files but nothing is thresholded to pure black and white. A page is converted only when that makes it at least 10% smaller. Errors (nothing is returned) if the result would not be smaller than the original, or if the PDF is unreadable, password-protected or over 100 pages.

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

Input Schema

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

Behavior5/5

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

Goes well beyond the annotations, which only declare it safe and idempotent. It discloses that text becomes non-selectable, colour is dropped, shading/photos kept, per-page conversion only happens with a 10% size win, and exactly when the operation errors out with no result. This is rich behavioral context an agent needs before calling.

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?

Dense but front-loaded, leading with the transformation and tradeoffs before the error conditions. It is a single long paragraph that stays on task, with only minor redundancy around the black-and-white comparison.

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?

With no output schema, the description carries return behavior and instead explains that errors return nothing, plus the exact preconditions and per-page conversion rule. For a compression tool with annotations covering safety, this leaves nothing an agent needs 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?

Schema coverage is 100%, so both parameters are already documented in the schema, setting the baseline at 3. The description reinforces the 100 dpi greyscale output and the 100-page/20 MB limits but adds little syntax or format detail beyond what the schema already provides for dpi and fileBase64.

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?

States a specific verb and resource ('shrink a scanned PDF') and details the exact transformation (pages to 100 dpi greyscale JPEG). It implicitly separates itself from the black-and-white sibling tools by noting it is 'larger than the black-and-white files' but not thresholded, though it never names those siblings explicitly.

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?

Gives clear conditions of use and the failure conditions (unreadable, password-protected, over 100 pages, result not smaller). It positions itself against the black-and-white variants via the size/quality tradeoff, but stops short of explicitly directing the agent to choose a specific sibling tool.

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?