FreeDailyPro Tools

csv_to_pptx

Read-onlyIdempotent

Turn a CSV file into an editable PowerPoint (.pptx, base64) of table slides from freedailypro: a cover slide, then the header and up to rowsPerSlide (default 12, max 40) rows on each slide, titled 'Title (1 of 3)'. The first row holds the column names unless header is false. The delimiter (comma, semicolon or tab) is found from the first line. At most 12 columns and 200 slides; cells are kept as plain text. Themes clean, dark, corporate, warm, minimal, or a brand.

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": {
      "csv": "<csv>"
    },
    "name": "csv_to_pptx"
  }
}

Input Schema

Name	Required	Description
`csv`	Yes	The CSV text (up to 10 MB)
`brand`	No	A theme made from a brand colour and fonts. Replaces theme.
`theme`	No	Built-in look. Default clean. Ignored when brand is given.
`title`	No	Deck and slide title. Default Data.
`header`	No	The first row holds column names. Default true.
`delimiter`	No	One character, or tab. Default: detected.
`titleSlide`	No	Add a cover slide with the title and the table size. Default true.
`rowsPerSlide`	No	Data rows per slide. Default 12.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 28, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly, non-destructive, idempotent, and closed-world behavior, so the safety profile is covered. The description adds substantial context beyond that: it explains the generated cover slide, slide titling, header-row handling, delimiter auto-detection, cell plain-text treatment, and hard limits of 12 columns and 200 slides. It could go slightly further on error behavior or exact base64 packaging, but it is already rich.

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 with the core purpose and then packs in useful constraints without redundancy. It is a single dense sentence, so structure could be improved with paragraph breaks, but nearly every clause earns its place; 'from freedailypro' is the only phrase that feels extraneous.

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 a complex conversion with eight parameters, a nested object, and no output schema, the description covers purpose, output format, slide structure, limits, defaults, and theme choices. It does not describe return packaging details beyond 'base64' or error cases, but combined with the fully documented input schema it is largely complete.

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 schema already documents all eight parameters, including the nested brand object and the theme enum. The description restates a few defaults and constraints (rowsPerSlide default 12/max 40, header false handling, delimiter detection, theme list) but adds little beyond what the schema already provides, making the baseline 3 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?

The description states a specific verb and resource: 'Turn a CSV file into an editable PowerPoint (.pptx, base64) of table slides.' It clearly distinguishes this from siblings like json_to_pptx or markdown_to_pptx by naming the input format and output artifact, and it specifies the slide structure up front.

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?

The usage is implied by the purpose: if you have CSV text and want a PPTX table deck, use this tool. However, the description does not explicitly say when to prefer this over sibling tools such as json_to_pptx, markdown_to_pptx, or text_csv, nor does it state any exclusions or prerequisites.

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?