FreeDailyPro Tools

pptx_resize

Read-onlyIdempotent

Change the slide size of a PowerPoint (.pptx) from freedailypro and scale the content to match, returning the new .pptx (base64). preset 16x9, 4x3, 16x10, a4 or letter, or width and height with a unit. mode fit (default) keeps the shape of the content and centres it; fill covers the new area; stretch changes the shape. Fonts, line widths and spacing scale with the content unless scaleText is false. The result lists how many shapes now reach outside the slide. Errors (422) when the slides are already that size.

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

Input Schema

Name	Required	Description
`mode`	No	Default fit
`unit`	No	Unit of width and height. Default in.
`width`	No	Custom width, with height
`height`	No	Custom height, with width
`preset`	No	A standard size (landscape)
`scaleText`	No	Scale text, lines and spacing too. Default true.
`fileBase64`	Yes	The presentation (.pptx), base64 encoded. Up to 50 MB and 500 slides. Old .ppt files and password-protected files are not supported.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 28, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Adds substantial context beyond the readOnly/idempotent annotations: mode semantics (fit keeps shape and centres, fill covers, stretch distorts), that fonts/lines/spacing scale unless scaleText is false, that the response includes a count of shapes now outside the slide, and the 422 no-op error. This is the kind of behavioral detail an agent cannot infer from structured fields.

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?

Tight and front-loaded: purpose first, then sizing options, then mode/font behavior, then outcome and error. The stray 'from freedailypro' clause is noise that doesn't earn its place, but overall density is high.

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 compensates by stating what is returned (new base64 pptx plus an out-of-bounds shape count), and input limits live in the schema. A brief note on error payload shape or original-file preservation would make it fully self-sufficient.

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, but the description goes further by enumerating presets (16x9, 4x3, 16x10, a4, letter), tying width/height to a unit, and explaining mode and scaleText effects rather than just naming defaults.

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 ('Change the slide size of a PowerPoint (.pptx)') plus the immediate consequence (scale content, return the new file). It is unmistakable against siblings like pptx_compress_* or pptx_split, which act on other aspects of the same file type.

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?

Explains concrete usage paths: pick a preset or supply width/height with a unit, and choose a mode. It also warns that a 422 is returned when the deck is already the target size, which steers callers away from a pointless call. It doesn't name a sibling alternative, but for a resize operation there isn't an obvious one.

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?