ChatPPT

by ParkerDiamond

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

slide_delete

Destructive

Permanently remove one or more slides from a presentation while cleaning up registry and collection references.

Instructions

Permanently delete one or more slides from the presentation and registry, and clean up collection references.

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>",
      "slideIds": "<slideIds>"
    },
    "name": "slide_delete"
  }
}

Input Schema

Name	Required	Description	Default
`deckId`	Yes	Stable ID of the presentation deck
`slideIds`	Yes	Array of slide IDs to delete

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 13, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations only declare destructiveHint=true, but the description adds real behavioral context: the deletion is permanent, it affects the registry as well as the presentation, and it cascades to 'clean up collection references'. It still omits whether child elements are removed and what happens if an ID in the array is missing, which keeps it from a 5.

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 that leads with the destructive verb and enumerates the affected stores with zero filler. Every clause earns its place.

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

Completeness4/5

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

For a two-parameter destructive mutation with no output schema, the definition covers permanence, what is deleted, and the reference-cleanup side effect. It is slightly thin on return value and partial-failure behavior when some slide IDs are invalid.

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 both deckId and slideIds are already documented, and the array's minItems=1 is visible in the schema. The description's 'one or more slides' merely restates that constraint rather than adding format or edge-case semantics, so the baseline of 3 applies.

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 ('Permanently delete one or more slides'), matching the batch nature of slideIds and naming the scope ('from the presentation and registry'). It does not explicitly differentiate itself from the sibling slide_collection_delete or element_delete, so it stops short of a 5.

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 guidance: nothing explains when to delete a slide versus removing it from a collection (slide_collection_delete) or deleting its elements (element_delete). The only implied usage signal is the word 'Permanently', which hints at irreversibility but is not framed as guidance.

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