Skip to main content
Glama
Sign In
PresentationMcpServer

PresentationMcpServer

by CompSciGuyIT
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Delete deck

delete_deck

Delete a deck bundle after user confirmation. Requires confirm:true to proceed.

Instructions

Delete a deck bundle. Refuses unless confirm:true.

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>",
      "confirm": "<confirm>"
    },
    "name": "delete_deck"
  }
}

Input Schema

NameRequiredDescriptionDefault
deckIdYes
confirmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/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 for behavioral disclosure. It does disclose the confirm:true requirement, which is a key safety guard, but it omits important details like irreversibility, required permissions, or success/failure behavior. This is a partial disclosure, not a complete one.

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 exactly two sentences with zero wasted words. It front-loads the purpose and immediately follows with the critical confirm constraint. Perfectly concise.

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?

The tool has simple parameters and no output schema, but the description still leaves gaps. It doesn't explain what happens on successful deletion, whether the action is permanent, or any error conditions beyond 'refuses.' For a delete tool, this is minimally adequate but not complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It adds meaning for the 'confirm' parameter by explicitly tying it to the refusal behavior, but it provides no detail on 'deckId' beyond what the name implies. This is insufficient given the lack of schema descriptions.

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 uses a specific verb ('Delete') and resource ('a deck bundle'), clearly distinguishing it from sibling tools like get_deck and list_decks. It also adds a behavioral qualifier ('Refuses unless confirm:true') that further clarifies the action.

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?

No guidance is provided on when to use this tool versus alternatives, such as get_deck for viewing or render_deck for presentation. The only hint is the confirm requirement, but that is a precondition, not usage context.

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