Skip to main content
Glama

compile_presentation

Converts rendered Manim slide assets into an interactive presentation, choosing output formats like HTML, PDF, or PPTX. Use it to combine multiple scenes into a single distributable deck.

Instructions

Compile rendered Manim-Slides scenes using manim-slides convert.

Wraps ``manim-slides convert`` to turn rendered slide assets into an
interactive presentation (e.g., Reveal.js HTML, PDF, or PPTX).

Args:
    scenes: Names of the rendered Scene/Slide classes to include, in order.
    dest: Destination path for the compiled presentation
        (e.g., "presentation.html"). The format is inferred from the
        extension when ``output_format`` is "auto".
    folder: Directory containing the rendered slide assets (default "slides").
    output_format: Conversion format: "auto", "html", "pdf", "pptx", or "zip".
    config: Extra converter options as key/value pairs
        (e.g., {"slide_number": "true"}).
    one_file: Embed all local assets (e.g., videos) into a single output file.
    workspace_dir: Working directory for the conversion. Defaults to the
        ``WORKSPACE_DIR`` environment variable or the current directory.
    timeout: Maximum time in seconds to wait for the conversion.

Returns:
    A JSON string with the conversion status, output destination,
    executed command, and captured stdout/stderr.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
destYes
configNo
folderNoslides
scenesYes
timeoutNo
one_fileNo
output_formatNoauto
workspace_dirNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations provided, the description carries the full burden, and it delivers substantial behavioral detail: it wraps an external command, returns a JSON status string with the executed command and stdout/stderr, infers output format from extension, embeds assets with one_file, and respects workspace_dir and timeout defaults. This goes well beyond a terse 'Compiles a presentation' statement.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with a one-sentence summary, followed by a compact 'Wraps ...' clarification and a structured Args block. For an 8-parameter tool this is appropriately sized, and every section adds value without filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 8 parameters, no annotations, and no schema descriptions, this description is complete: it explains input prerequisites, output format behavior, file location, environment default, timeout, and return value. It provides enough information for an agent to select and invoke the tool correctly.

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 description coverage is 0%, but the Args section documents all 8 parameters with semantic meaning: scenes, dest, folder, output_format, config, one_file, workspace_dir, and timeout. It adds examples and default behavior, fully compensating for the lack of schema descriptions.

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 opens with a specific verb+resource: 'Compile rendered Manim-Slides scenes using manim-slides convert.' It further clarifies that it produces interactive presentation assets such as Reveal.js HTML, PDF, or PPTX, which clearly distinguishes this compilation tool from sibling rendering, preview, and serving tools.

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?

It provides clear context by explaining that this tool consumes rendered slide assets and turns them into an interactive presentation, implying it should be used after rendering and before serving. However, it does not explicitly name alternatives or state when-not-to-use conditions relative to sibling tools like export_revealjs_html or serve_revealjs_html.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/antoniomachuca/MCP-Manim-Slides'

If you have feedback or need assistance with the MCP directory API, please join our Discord server