FreeDailyPro Tools

pptx_compress_strong

Read-onlyIdempotent

Compress a PowerPoint (.pptx) from freedailypro at the Strong level, the smallest of the three: pictures up to 110 dpi at JPEG quality 58. Fine on screen, soft in print. Pictures (JPEG, PNG, BMP) are re-saved smaller, unused layouts and the preview picture are removed, and the file is re-packed at maximum compression; text, charts, animations, audio and video are left exactly as they are, so the deck stays fully editable. Always returns the .pptx as base64 plus originalBytes, outputBytes, reductionPercent and the pictures changed, even when it could not get smaller (a note says so).

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": "pptx_compress_strong"
  }
}

Input Schema

Name	Required	Description
`maxDpi`	No	Never keep pictures sharper than this many dpi (48 to 300), on top of the level.
`fileBase64`	Yes	The presentation (.pptx), base64 encoded. Up to 50 MB and 500 slides. Old .ppt files and password-protected files are not supported.
`removeNotes`	No	Also remove speaker notes first. Default false.
`removeThumbnail`	No	Remove the stored preview picture. Default true; send false to keep it.
`removeUnusedLayouts`	No	Remove slide layouts no slide uses, and the pictures only they carry. Default true; send false to keep them.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 6, 2026

changedInput schema / properties / removeThumbnail / description

Previous value: -"Also remove the stored preview picture. Default false."New value: +"Remove the stored preview picture. Default true; send false to keep it."

changedInput schema / properties / removeUnusedLayouts / description

Previous value: -"Also remove slide layouts no slide uses, and the pictures only they carry. Default false."New value: +"Remove slide layouts no slide uses, and the pictures only they carry. Default true; send false to keep them."

AddedOct 28, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only declare the safety profile (readOnly, idempotent, non-destructive); the description adds the substance an agent actually needs — exactly what is degraded (JPEG/PNG/BMP pictures re-saved, layouts and preview picture stripped) versus what is untouched (text, charts, animations, audio, video, editability preserved). It also discloses the always-return contract including the failure case where the file could not get smaller and a note explains why.

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?

Front-loaded with the level definition and its quality trade-off, then the mechanics, then the return contract — a sensible order with no filler. The single dense run-on sentence carrying the mechanics is slightly heavy, but every clause adds information rather than repeating the name or schema.

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?

There is no output schema, and the description compensates by naming the return payload (base64 plus originalBytes, outputBytes, reductionPercent, pictures changed) and the note-on-no-improvement case. Combined with the schema's input limits (50 MB, 500 slides, no .ppt or password-protected files), an agent has everything needed to call and interpret this tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, and the description does partly restate defaults for thumbnail and unused-layout removal. It still adds consequence-level meaning: it spells out that pictures in JPEG/PNG/BMP get re-saved smaller, that only pictures carried by unused layouts go with them, and that the file is re-packed at maximum compression — outcome detail the terse flag descriptions do not carry.

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?

States a specific verb and resource (compress a .pptx) and pins the level precisely: "the smallest of the three: pictures up to 110 dpi at JPEG quality 58." That positional framing plus the concrete dpi/quality numbers lets an agent separate it from pptx_compress_default, pptx_compress_medium and pptx_compress_size without opening any schema.

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?

"Fine on screen, soft in print" gives a usable selection heuristic against the gentler levels, and "the smallest of the three" signals the alternatives exist. It stops short of explicitly naming the sibling tools or stating a when-not-to-use rule (e.g. use default when print quality matters), so it is clear context rather than full routing guidance.

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?