Skip to main content
Glama
Sign In
ChatPPT

ChatPPT

by ParkerDiamond
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

slide_collection_create

Create a named, ordered group of existing slides within a presentation deck to organize related content and make slide navigation easier.

Instructions

Create a named ordered collection/group of existing slides within a presentation deck.

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": {
      "deckId": "<deckId>",
      "name": "<name>"
    },
    "name": "slide_collection_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesCollection name
deckIdYesStable ID of the presentation deck
slideIdsNoOrdered list of slide IDs belonging to this collection
descriptionNoOptional description

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it discloses only that the collection is named and ordered. It does not say whether slides can belong to multiple collections, whether slideIds may be empty (schema default suggests yes), whether the operation is idempotent, what happens on duplicate names, or what is returned. For a mutation tool with zero annotation coverage this is a substantial gap.

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 no filler or hedging. The only minor inefficiency is the 'collection/group' doublet, which could be one term.

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?

With four parameters, two required, and no output schema or annotations, the description covers the core concept but leaves important operational facts unstated: empty-collection behavior, membership semantics across collections, and failure modes. Adequate as a minimum viable definition, but not complete for a mutation tool.

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 100%, so the schema already documents all four parameters. The description adds the useful semantic that the collection is 'named' and 'ordered' and that slides must be 'existing', which maps meaning on top of slideIds and deckId, but adds no format, constraint, or edge-case detail. Baseline 3 is appropriate.

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 states a specific verb and resource ('Create a named ordered collection/group of existing slides') and clarifies the scope ('within a presentation deck'), which distinguishes it from slide_create since it groups rather than creates slides. It stops short of naming sibling tools, so differentiation is inferable but not explicit.

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-to-use guidance, no mention of prerequisites such as slides needing to already exist in the deck, and no reference to alternatives like slide_move or slide_collection_update. The agent must infer the decision context entirely.

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