Skip to main content
Glama

decken_reconstruct_deck

Reconstructs up to 24 ordered slide images into one native editable PowerPoint (.pptx) presentation, using async job polling to track completion.

Instructions

Reconstruct multiple slide images (1 to 24 pages) into a single multi-slide native editable PowerPoint (.pptx) presentation using async job polling.

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

Input Schema

NameRequiredDescriptionDefault
modelIdNo
deckTitleNo
engineModeNovlm
imagePathsYesOrdered list of local slide image paths.
outputPathYesDestination path for the combined .pptx presentation.
previewDirNoOptional directory to save per-slide rendered PNG previews.
pollIntervalMsNo
maxOutputTokensNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.2/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 burden. It does disclose important behavior—asynchronous execution and native editable PowerPoint output—but omits operational details such as overwrite behavior for outputPath, what is returned after starting the job, failure handling, and how polling should proceed.

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 a single front-loaded sentence with no filler. Every clause contributes useful information about input, output, and execution model.

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

Completeness2/5

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

For an 8-parameter file-producing tool with no annotations, no output schema, and low parameter documentation coverage, the description is too thin. It should explain the async workflow, key optional parameters, and output-path behavior to be sufficient.

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

Parameters2/5

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

Schema description coverage is only 38% across 8 parameters. The description mentions the page limit and PPTX output, which largely restate schema constraints, and does not clarify modelId, deckTitle, engineMode, previewDir, pollIntervalMs, or maxOutputTokens.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource: reconstruct multiple slide images into a single multi-slide editable PPTX. It also states the 1-to-24 page scope, which distinguishes it from a single-slide reconstruction sibling, though it does not name that sibling explicitly.

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

Usage Guidelines3/5

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

The mention of 'async job polling' implies a follow-up workflow, likely using decken_job_status, but the description does not explicitly explain when to use this tool versus decken_reconstruct_slide, decken_generate, or the job-status tools. The usage context is implied rather than spelled out.

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