Skip to main content
Glama
leanzero-srl

MCP Document Processor

Official
by leanzero-srl

edit-pptx

Edit existing PowerPoint files: preview slide outline, append slides from markdown, or replace a specific slide by index. Rebuilds text and notes, not charts or images.

Instructions

Edit an existing PowerPoint (.pptx). Actions: 'preview' (show the current slide outline), 'append-slides' (add new slides from markdown — one '## ' heading per slide), 'replace-slide' (replace one content slide by 1-based index with new markdown). IMPORTANT: edit-pptx REBUILDS the deck from the existing slides' extracted TEXT + speaker notes, normalized to a style preset — charts, images, and exact original formatting on pre-existing slides are NOT preserved (best for the text/bullet decks create-pptx makes). To author a brand-new deck use create-pptx; to read a deck use read-doc.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
styleNoAdvanced style overrides merged on top of stylePreset.
titleNoOptional heading to use when replace-slide content has no leading '## '.
actionYesEdit action.
contentNoNew slide markdown ('## ' per slide). Required for append-slides and replace-slide.
filePathYesPath to the existing .pptx file.
uploadUrlNoOPTIONAL. HTTPS URL of a receiver that will accept a JSON envelope `{data:base64, filename, mimeType, size}` POSTed with this Bearer auth. If you have NOT been given an uploadUrl in your context, OMIT this field and the tool just writes the file locally. Single-use semantics — do not retry on 4xx. Works with any compliant receiver (CogniRunner attachment-upload web trigger is the reference implementation, but the contract is generic).
clientHintNoHow the response should be shaped. 'interactive' = polished one-line message for end-users (no chatty registry/lineage notes). 'agent' = verbose response with all metadata for AI consumption. 'auto' (default) = detect from input shape or MCP_CLIENT_TYPE env var, falling back to 'agent'.
outputPathNoOptional. Write the result here instead of overwriting the input file.
slideIndexNo1-based index among CONTENT slides (the title slide is excluded). Required for replace-slide.
stylePresetNoStyle preset. 'claude-like' (modern blue-accented professional) is the default for general-purpose docs. 'professional' is the executive serif look. Auto-selected from category if omitted.
uploadFilenameNoOPTIONAL. Filename to put in the upload envelope. Defaults to the local file's basename. Useful when the local file got auto-suffixed (e.g. duplicate prevention) and you want a clean name on the receiver side.
uploadAuthHeaderNoOPTIONAL. Authorization header value for uploadUrl (e.g. 'Bearer abc123'). REQUIRED when uploadUrl is set; ignored otherwise. Never logged.
Behavior5/5

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

With no annotations provided, the description fully discloses critical behavioral traits: the tool REBUILDS the deck, extracts text and speaker notes, normalizes to a style preset, and does NOT preserve charts, images, or exact original formatting. This level of transparency is exemplary for a mutation tool.

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 efficiently structured: purpose first, then actions, then critical behavioral caveat (IMPORTANT), then sibling guidance. Every sentence provides necessary context without redundancy. It is appropriately sized for the tool's complexity.

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 the tool's complexity (12 parameters, 3 actions, significant side effects), the description covers purpose, actions, behavioral implications, and tool selection guidance comprehensively. No output schema exists, but the description sufficiently explains what each action produces (preview shows outline, append/replace modifies file).

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 description coverage is 100%, so the schema already documents all parameters. The description adds action-specific context (e.g., 'one '## ' heading per slide' for content, '1-based index among CONTENT slides' for slideIndex) and explains the uploadUrl workflow. While the schema is clear, the description enhances understanding of how parameters interact with actions.

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 'Edit an existing PowerPoint (.pptx)' and enumerates three specific actions ('preview', 'append-slides', 'replace-slide'), clearly stating the tool's purpose. It distinguishes itself from siblings by explicitly naming create-pptx and read-doc, ensuring the agent understands the tool's scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit when-to-use and when-not-to-use guidance: 'To author a brand-new deck use create-pptx; to read a deck use read-doc.' It also notes that the tool is best for text/bullet decks from create-pptx and warns about loss of charts/images, giving clear context for appropriate usage.

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/leanzero-srl/leanzero-mcp-doc-processor'

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