ai-slides-mcp

by vuhai2002

Overview Schema Source Related Servers Discussions Admin

generate_slide_deck

Convert slide content prompts into a styled PowerPoint deck by generating one image per prompt and assembling them. Enable enhance mode for clean editorial slide design.

Instructions

Generate one image per prompt then assemble them into a PPTX deck.

Each prompt should be the CONTENT of one slide. style='slide' (default here) applies a clean editorial presentation design (light, restrained accent, one hero visual, short labels, takeaway banner) — pass raw slide content and the enhancer designs it. Set enhance=False to send prompts verbatim.

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": {
      "prompts": "<prompts>"
    },
    "name": "generate_slide_deck"
  }
}

Input Schema

Name	Required	Default
`prompts`	Yes
`aspect`	No	16:9
`out_pptx`	No	deck.pptx
`out_dir`	No	out
`enhance`	No
`style`	No	slide

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 13, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses the core behavior (generating images and assembling into PPTX) and explains the effect of the style and enhance parameters. It does not contradict any annotations and adds sufficient context for safe invocation.

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 efficient, with the main action in the first sentence. Subsequent sentences add necessary detail without fluff. Slightly longer than ideal but earns its length.

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?

Given 6 parameters and no output schema, the description covers the purpose, all parameters, and behavioral choices. It does not discuss return values or errors, but for a generation tool this is acceptable. It provides enough context for correct use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate. It adds meaning to each parameter: 'prompts' as 'CONTENT of one slide', explains the default style, and clarifies the enhance flag. This goes well beyond the raw schema, making the parameters understandable.

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 starts with 'Generate one image per prompt then assemble them into a PPTX deck,' clearly stating the verb and resource. It distinguishes from siblings by detailing the style and enhance options, which are specific to this tool.

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?

The description provides explicit guidance on using the style parameter ('style='slide' (default here) applies a clean editorial presentation design') and the enhance parameter ('Set enhance=False to send prompts verbatim'). It implies the intended use case for slide decks but does not explicitly mention when not to use it or alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server