FreeDailyPro Tools

pptx_compress_medium

Read-onlyIdempotent

Compress a PowerPoint (.pptx) from freedailypro at the Medium level: pictures up to 150 dpi at JPEG quality 72, and opaque PNG photos are re-saved as JPEG when that is under half the size. Good for email. 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_medium"
  }
}

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/5.0

Behavior4/5

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

Goes well beyond the annotations by disclosing exactly what is destroyed (unused layouts, preview picture, picture resolution), what is preserved (text, charts, animations, audio, video, editability), and the return payload plus the important edge case that it still returns the file when no reduction was possible. It does not cover the input limits, though the schema does, so it is strong but not exhaustive.

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 verb and resource, and every sentence adds operational detail. It is dense to the point of being one long block, and the 'Pictures (JPEG, PNG, BMP) are re-saved smaller' clause repeats what the opening sentence already established.

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 takes on the return-value burden itself and does so: base64 payload plus originalBytes, outputBytes, reductionPercent and the changed-picture list, including the no-reduction case. Combined with the fully documented schema, 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.

Parameters3/5

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

Schema coverage is 100%, so the per-parameter descriptions already carry the semantics. The description adds a little context by describing the level's baseline behaviour and the thumbnail removal, but it never explains the maxDpi interaction or removeNotes beyond what the schema says. Baseline 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?

States a specific verb and resource ('Compress a PowerPoint (.pptx)') and pins the 'Medium level' to concrete settings (150 dpi, JPEG quality 72, opaque PNG photos re-saved as JPEG under half the size). Those numbers let an agent distinguish it from the sibling levels pptx_compress_default, pptx_compress_strong 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 Guidelines3/5

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

'Good for email' gives a rough usage context, but there is no explicit when-to-use versus the three sibling compression levels and no statement of when-not-to-use it. The agent must infer that Medium sits between default and strong from the numbers alone.

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?