delete_slide_presentation
Permanently delete a slide presentation (slides, powerpoint, deck, keynote).
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Presentation ID |
Mila
by gg.mila.mcp
TDQS
A4/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. 'Permanently delete' discloses the irreversible nature, which is important. It doesn't mention permissions or side effects, but for a simple delete-by-ID tool, this is adequate but not rich.
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 concise sentence, front-loaded with the essential verb and object. It wastes no words and includes useful synonyms in parentheses.
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 low-complexity tool with one parameter and no output schema, the description covers the core behavior and irreversibility. It could mention potential side effects or prerequisites, but the simplicity of the operation makes it nearly complete.
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?
The input schema covers 100% of the parameter (id with description 'Presentation ID'). The description adds no extra semantic meaning beyond the schema, so the baseline score of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb ('delete') and a specific resource ('slide presentation'), with clarifying synonyms. It clearly distinguishes from sibling delete tools like delete_document and delete_sheet.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description makes clear the tool is for slide presentations, providing context on when to use it. It doesn't explicitly mention exclusions or alternatives, but the resource type is unambiguous given the tool name and synonyms.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A3.7/5.0
Disambiguation5/5
Every tool targets a distinct resource and action: document, sheet, tab, or presentation. Even similar operations like append_rows, append_slides, and append_to_document are clearly differentiated by their intended target.
Naming Consistency4/5
The naming follows a predictable verb_noun pattern with create_, get_, list_, update_, delete_, and append_. Minor deviations like append_to_document (uses 'to') and the use of 'slide_presentation' vs 'slides' keep it from being perfectly uniform.
Tool Count4/5
At 23 tools, the count is slightly above the ideal range, but each tool serves a clear purpose across three resource types (documents, sheets, slides). The volume is justified by supporting tab-level operations and append functionality.
Completeness4/5
The server provides full CRUD plus listing for each resource type, along with tab management and append operations. Minor gaps exist, such as lack of a direct 'set cell value' operation and no slide reorder or delete individual slide, but core workflows are well covered.