FreeDailyPro Tools

markdown_to_pptx

Read-onlyIdempotent

Turn Markdown or a plain outline into an editable PowerPoint (.pptx, base64) from freedailypro, with real title and body placeholders (so Outline view, the slide master and accessibility checks work). # Title makes the title slide (a short line under it is the subtitle), ## Heading a new slide, ### Heading a bold sub-heading, - item / 1. item bullets (indent two spaces for sub-bullets), | a | b | tables, Note: text speaker notes, --- ends a slide, bold, italic, code and links work. Pictures given by web address are not fetched (reported in warnings); use json_to_pptx to put pictures in. mode outline reads an indented outline instead (first line = deck title). Themes: clean, dark, corporate, warm, minimal, or a brand colour and fonts.

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": {
      "markdown": "<markdown>"
    },
    "name": "markdown_to_pptx"
  }
}

Input Schema

Name	Required	Description
`mode`	No	Default markdown
`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.
`markdown`	Yes	The deck as Markdown (or an indented outline in outline mode)

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 28, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds real value beyond them: output is editable with genuine title/body placeholders so Outline view, master and accessibility checks work, URL images are skipped and surfaced in warnings, and theme is ignored when brand is supplied. It stops short of describing the warnings payload or size/time limits.

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-loads the outcome and the editable-slide guarantee, then packs syntax, limitations and theming into a tight block with zero filler. The single dense sentence enumerating inline styles is readable but borders on a run-on.

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 correctly carries the return contract (base64 .pptx) and the key failure mode (unfetched URL images). Coverage of theming and modes is thorough; only the warnings/error detail and length ceiling handling are left unstated.

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 already 100%, so this is bonus territory, and the description does add meaning — the Markdown grammar that markdown accepts, the outline-mode reinterpretation of the same field, and theme-vs-brand precedence. It doesn't spell out indent depth beyond two spaces or how deeply nested brand overrides interact.

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 artifact — turn Markdown or an outline into an editable .pptx returned as base64 — and immediately distinguishes itself from the sibling json_to_pptx for image-bearing decks. The named markup constructs make the input contract unambiguous at a glance.

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?

Explicitly routes picture-containing decks to json_to_pptx and explains when to pick mode=outline (indented outline, first line = deck title). It stops short of positioning against csv_to_pptx or stating when a deck should be templated instead, so it is clear context without full alternatives coverage.

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?