Skip to main content
Glama

decken_reconstruct_slide

Reconstruct a PNG, JPEG, or WebP slide image into a native editable PowerPoint (.pptx) file with real shapes, tables, and inpainted backgrounds for direct editing.

Instructions

Reconstruct a single slide image (PNG, JPEG, WebP) into a 100% native editable PowerPoint (.pptx) file with <p:sp> shapes, <a:tbl> tables, and Harmonic Laplace Inpainted backgrounds.

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": {
      "outputPath": "<outputPath>"
    },
    "name": "decken_reconstruct_slide"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelIdNoExplicit VLM model ID (defaults to qwen/qwen3.8-flash).
slideIdNo
imageUrlNoPublic https:// URL to the input slide image (zero base64 context overhead).
deckTitleNo
imagePathNoLocal path to the input slide image (or https:// URL).
engineModeNovlm
outputPathYesDestination path to write the compiled .pptx file.
imageDataUrlNoAlternative Base64 data URL if no local file or URL is used.
maxOutputTokensNo
previewOutputPathNoOptional path to save the rendered PNG preview.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does disclose the transformation semantics and output fidelity (native <p:sp> shapes, <a:tbl> tables, inpainted backgrounds), which is real value, but it says nothing about cost/latency, model dependencies, failure modes, or what happens to the file at outputPath.

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?

A single front-loaded sentence with the core action first and the output characteristics trailing. It is dense with jargon (<p:sp>, <a:tbl>, Harmonic Laplace Inpainting) but every clause is substantive rather than filler.

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

Completeness3/5

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

For a 10-parameter tool with no annotations and no output schema, the description explains the output well but leaves the input-side decisions under-explained: three overlapping image source parameters and an engineMode enum with no stated tradeoff. Adequate to call, not adequate to call optimally.

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 description coverage is 60%, and the description adds only format support (PNG, JPEG, WebP), which mildly informs the three mutually exclusive image source parameters (imageUrl, imagePath, imageDataUrl). It gives no guidance on choosing among those alternatives or on the vlm vs deterministic engineMode, which are the decisions an agent most needs help with.

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 (Reconstruct) plus the exact resource (a single slide image) and the produced artifact (a native editable .pptx with real shapes and tables). The phrase 'single slide' implicitly separates it from decken_reconstruct_deck, so an agent can pick between them without opening either schema.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not guidance, no mention of when the deck-level sibling is preferable, and no stated prerequisites (model availability, credentials, whether an existing output file is overwritten). Usage can only be inferred from the verb itself.

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