Skip to main content
Glama
Sign In
ChatPPT

ChatPPT

by ParkerDiamond
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

deck_create

Create a new blank PowerPoint presentation and initialize its metadata in the managed workspace so you can start building slides from a clean deck.

Instructions

Create a new blank PowerPoint presentation deck and initialize its metadata in the managed workspace.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "deck_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoTitle for the new presentation deck

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/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, and it does disclose two useful traits: the deck is blank and metadata is initialized in a managed workspace. It omits what happens if the title is omitted (the only parameter is optional), whether duplicate titles are rejected, and what identifier is returned for chaining into slide_create.

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?

A single front-loaded sentence with no filler; the verb and resource lead, and the scoping detail ('blank', 'managed workspace') follows. Nothing needs to be trimmed.

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 simple one-parameter creation tool with no output schema, the description is adequate but leaves out the return value (presumably a new deck identifier) that an agent needs to continue the workflow, and does not address the all-optional parameter set.

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 coverage is 100% for the single 'title' parameter, so the schema already defines its type and 1-200 length bounds. The description adds only the vague notion of 'metadata' initialization and does not say the title is optional or what default is applied when absent.

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?

States a specific verb and resource ('Create a new blank PowerPoint presentation deck') plus the side effect of initializing metadata in the managed workspace. This distinguishes it from deck_import (non-blank import) and deck_update, though it never names those siblings 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 word 'blank' implicitly signals this is for new decks rather than imported or existing ones, but there is no explicit when-to-use/when-not statement and no pointer to deck_import for existing files. An agent must infer the routing.

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

Deploy Server

Other Tools