FreeDailyPro Tools

pptx_compress_default

Read-onlyIdempotent

Compress a PowerPoint (.pptx) from freedailypro at the Default level, the sharpest: pictures are kept up to 220 dpi at JPEG quality 82, large photos get smaller, and nothing is converted from PNG to JPEG. 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_default"
  }
}

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

A3.7/5.0

Behavior5/5

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

Beyond the annotations, the description discloses the exact compression behavior: 220 dpi limit, JPEG quality 82, no PNG-to-JPEG conversion, removal of unused layouts and preview pictures, and preservation of text, charts, animations, audio, and video. It also explains the return payload and that a note is included when no size reduction is achieved, which is valuable behavioral context.

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 dense but front-loads the core action and then explains effects and return values. It is longer than ideal, and the 'freedailypro' branding and 'the sharpest' phrasing add minor noise, but most sentences carry useful information.

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, yet the description fully explains the return shape: base64 .pptx plus originalBytes, outputBytes, reductionPercent, and changed pictures, including the case where compression does not shrink the file. For a mutation-like compression tool, the preservation and removal behavior is also complete enough for an agent to call it correctly.

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 the input schema already documents all five parameters. The description adds some behavioral context about picture handling and the default compression level, but it does not add meaningful guidance for maxDpi or removeNotes beyond what the schema provides. Baseline 3 is appropriate.

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 states a specific verb and resource: compress a PowerPoint .pptx at the Default level. It also describes which elements shrink and which stay untouched, so the operation is recognizable. It stops short of naming the sibling compression presets, and the phrase 'the sharpest' is slightly ambiguous against siblings like pptx_compress_medium and pptx_compress_strong.

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

Usage Guidelines2/5

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

The description explains what the Default level does but gives no explicit guidance on when to choose it over pptx_compress_medium, pptx_compress_strong, pptx_compress_size, or pptx_clean. An agent must infer from the preset name alone whether to use this tool or a sibling.

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?