ChatPPT

Overview Schema Source Related Servers Discussions Admin

deck_import

Import an existing PowerPoint deck into the managed workspace and initialize its registry metadata, making it available for editing through ChatPPT.

Instructions

Import an existing PowerPoint deck into the managed workspace and initialize its registry metadata.

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": {
      "filePath": "<filePath>"
    },
    "name": "deck_import"
  }
}

Input Schema

Name	Required	Description	Default
`filePath`	Yes	Path to an existing PowerPoint presentation file

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 13, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries the full behavioral burden and falls short. It does not say whether the source file is copied or referenced, how name collisions are handled, whether the import is reversible, or what happens to registry metadata on failure. 'Initialize its registry metadata' hints at a side effect but never explains its consequences.

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?

One sentence, front-loaded with the action and resource, with no filler or redundancy. It is efficient, though its brevity is partly a symptom of under-specification rather than disciplined concision.

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 a mutating import operation with no annotations and no output schema, the definition is too thin. An agent cannot tell what identifier the import returns for use with deck_read or deck_update, whether duplicates are created, or what permissions the workspace requires.

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?

There is a single parameter with 100% schema description coverage ('Path to an existing PowerPoint presentation file'), so the schema already does the work and the baseline of 3 applies. The description adds no format constraints, path scope, or size limits beyond the schema.

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 uses a specific verb and resource: 'Import an existing PowerPoint deck into the managed workspace' plus 'initialize its registry metadata'. The word 'existing' implicitly separates it from deck_create, which is presumably for new decks, though no sibling is named.

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 explicit when-to-use or when-not-to-use guidance, no mention of prerequisites (e.g., file must exist locally, be closed, be a .pptx), and no statement contrasting it with deck_create or deck_validate. The only signal is the adjective 'existing', which is incidental rather than instructive.

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