FreeDailyPro Tools

pptx_slide_numbers

Read-onlyIdempotent

Add slide numbers to a PowerPoint (.pptx) from freedailypro, or remove them, and get the new .pptx (base64). The numbers are real slide-number fields, so they follow when slides move. Slides that already have a number are left alone. 'of-total' writes the total as plain text (PowerPoint has no total field). mode remove takes off the numbers the slides themselves carry (not those on the master).

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

Input Schema

Name	Required	Description
`mode`	No	Default add
`size`	No	Points. Default 12.
`color`	No	Hex colour, for example 595959
`format`	No	3, Slide 3 or 3 / 12. Default number.
`startAt`	No	Number of the first slide. Default 1; 0 makes the second slide 1.
`position`	No	Default bottom-right
`skipFirst`	No	Leave the first slide without a number
`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.0

Behavior5/5

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

Annotations already declare read-only, idempotent, and non-destructive behavior, but the description adds substantive context: real slide-number fields follow slides, existing numbers are left alone, 'of-total' is plain text because PowerPoint lacks a total field, and remove is slide-level only. These are meaningful behavioral details beyond structured annotations.

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 front-loaded, compact, and mostly free of waste. The phrase 'from freedailypro' is minor marketing noise, but it does not obscure the core instructions.

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?

For an eight-parameter transformation tool with no output schema, the description covers the purpose, output form, and key behavioral nuances well. Some edge-case or error behavior is left to the schema, but the critical agent-facing context is present.

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?

With 100% schema coverage, the baseline is 3. The description adds useful meaning for specific parameter choices, especially format=of-total and mode=remove, while leaving most other parameter details to the schema.

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 specific verbs (add/remove slide numbers) and the resource (.pptx), and says it returns a new base64 file. It is clearly distinguishable from PDF and other PPTX siblings by format, though it does not explicitly name an alternative tool.

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?

It explains the add/remove modes and clarifies that remove targets slide-level numbers, not master numbers. However, it does not explicitly state when to choose this tool over sibling PDF/PPTX tools or give broader usage exclusions.

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?