Skip to main content
Glama
MCP for PADI

MCP for PADI

by Mrc527

Delete dive

logbook_delete_dive
Destructive

Permanently delete a dive from a PADI logbook by dive id, confirming its title first. Locked or photo-bearing dives cannot be removed here.

Instructions

Delete a dive from the PADI logbook for good (PADI has no trash). Ask the user first, unless they clearly asked to delete this dive. confirm_title must be the dive's title (as logbook_get_dive shows it; case and spaces at the ends do not matter). Dives that are Pending, Verified or QR Code Verified are locked: they cannot be changed or deleted. Returns the deleted dive, so it can be created again with logbook_create_dive (as a new dive with a new id). Photos are not part of the returned dive: a dive that has photos is not deleted here (delete it on learning.padi.com, which also deletes its photos).

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": {
      "dive_id": "<dive_id>",
      "confirm_title": "<confirm_title>"
    },
    "name": "logbook_delete_dive"
  }
}

Input Schema

NameRequiredDescriptionDefault
dive_idYesThe dive id (from logbook_list_dives)
confirm_titleYesThe dive's title, exactly as in the logbook (case does not matter), to confirm the delete. For a dive without a title: its id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, but the description goes well past that: no trash/undo, state-based locking rules, the photo restriction that blocks deletion here, and what the call returns. It also states the recovery path (recreate via logbook_create_dive with a new id), which is essential context for a destructive tool.

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?

Front-loaded with the action and the ask-first safety rule, then the confirmation requirement, then the lock and photo exceptions. Dense but each sentence carries a distinct constraint; only the stacked parentheticals add slight reading friction.

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

Completeness5/5

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

Despite no output schema, the description explains the return (the deleted dive, minus photos) and its intended reuse. Locking behavior, confirmation token semantics, and the photo edge case are all covered, leaving nothing an agent needs before invoking.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description still adds value by tying confirm_title to the exact title surfaced by logbook_get_dive and noting trailing/leading spaces are ignored. The dive_id parameter is not elaborated beyond the schema's own pointer to logbook_list_dives.

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 opening sentence gives a specific verb and resource ("Delete a dive from the PADI logbook") and immediately qualifies permanence ("for good (PADI has no trash)"). This is unambiguously distinct from logbook_update_dive or logbook_create_dive.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit preconditions are given: ask the user first unless they clearly asked for this deletion, use confirm_title as shown by logbook_get_dive, and locked dives (Pending/Verified/QR Code Verified) cannot be deleted at all. It also routes photo-bearing dives to learning.padi.com and points to logbook_create_dive for recreation, so the agent knows both when to use it and when to go elsewhere.

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