Skip to main content
Glama
MCP for PADI

MCP for PADI

by Mrc527

Update dive

logbook_update_dive
Idempotent

Update an existing PADI logbook dive by changing only the fields you provide. Use null to clear optional fields; Pending, Verified, or QR Code Verified dives are locked.

Instructions

Change a dive in the PADI logbook. Only the fields you pass change; null clears an optional field (title, date, location and dive_type cannot be cleared). Same fields, values and units as logbook_create_dive. Numbers are in the call's units (see units): depth and visibility in m or ft, temperatures in degrees C or F, weight in kg or lb, cylinder size in litres or cubic feet, pressures in bar or psi, times in minutes. Dives that are Pending, Verified or QR Code Verified are locked: they cannot be changed or deleted. Returns the updated dive.

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

Input Schema

NameRequiredDescriptionDefault
gasNoBreathing gas: Air (Air (21% oxygen)), Enriched_32 (Nitrox EANx32 (32% oxygen)), Enriched_36 (Nitrox EANx36 (36% oxygen)), Enriched_40 (Nitrox EANx40 (40% oxygen)), Enriched (Nitrox, other mix), Trimix, Rebreather. "EAN32" or "nitrox 32" means Enriched_32. Air and EANx32/36/40 fill the percentages; Enriched, Trimix and Rebreather need oxygen_pct (and helium_pct for Trimix), summing to 100 with nitrogen (null clears it)
dateNoDive date YYYY-MM-DD (a calendar date, not in the future, at most 100 years ago)
suitNoExposure suit: NoExposure (No exposure suit), FullSuit_3mm (3 mm full wetsuit), FullSuit_5mm (5 mm full wetsuit), FullSuit_7mm (7 mm full wetsuit), Shorty, SemiDrySuit, DrySuit. "3mm" means FullSuit_3mm (null clears it)
notesNoNotes (free text) (null clears it)
surgeNoSurge: SomeSurge (Light surge), MediumSurge, BigSurge (Strong surge). "strong" means BigSurge; "none" means no surge (null clears it)
titleNoNew title
unitsNoUnits of the numbers in this call and its answer: auto (the PADI logbook setting), metric (m, degrees C, bar, kg, litres) or imperial (ft, degrees F, psi, lb, cubic feet). Default: the server setting.
wavesNoWaves: NoWaves, SmallWaves, MediumWaves, LargeWaves (null clears it)
skillsNoTraining dives only: the skills done (replaces the list) (null clears it). Open (flexible skills): "no skills", "cramp removal", "snorkel exchange", "tube deployment", "weight drop", "swim compass", "diver tow", "remove scuba", "remove weights", and for dives 2-4 also "controlled ascent", "compass navigation" ("no skills" when none was done). Rescue (exercises): "tired diver", "panicked diver", "responsive diver", "distressed diver underwater", "missing diver", "surfacing the unresponsive diver", "unresponsive diver at the surface", "exiting the unresponsive diver", "first aid for pressure", "unresponsive diver". Reactivate (requirements): "mask flood", "panicked diver", "weight drop", "alternate air", "log dive" ("panicked diver" is PADI's value of the "buoyancy / weight check" item). Specialty: one free-text entry (the specialty). Advanced and DSD dives store no skills. Open, Rescue and Reactivate dives need at least one before verification
statusNoPublish (a finished dive, the default) or Draft (an unfinished dive: depth and time not needed)
weightNoWeight carried, in kg (metric) or lb (imperial) (null clears it)
buddiesNoBuddies (one free-text field, for example "Sam, Kim") (null clears it)
currentNoCurrent: NoCurrent, SomeCurrent (Light current), MediumCurrent, StrongCurrent. "light" means SomeCurrent (null clears it)
dive_idYesThe dive id (from logbook_list_dives)
feelingNoHow the dive felt: Amazing, Good, Average, Poor (null clears it)
time_inNoTime in, HH:MM (not verified with PADI yet; PADI's web app does not show it) (null clears it)
weatherNoWeather: Sunny, Partly Cloudy, Cloudy, Rainy, Windy, Foggy (null clears it)
air_tempNoAir temperature, in C (metric) or F (imperial) (null clears it)
locationNoNew location
time_outNoTime out, HH:MM (not verified with PADI yet; PADI's web app does not show it) (null clears it)
dive_typeNoDive type: Boat, BeachShore (Shore), Other. "shore" and "beach" mean BeachShore
equipmentNoExtra equipment, for example ["Hood", "Gloves", "Boots"] (PADI offers these three; other items are allowed). Replaces the whole list (null clears it)
max_depthNoMaximum depth, in m (metric) or ft (imperial). Needed unless the dive is a Draft (null clears it)
helium_pctNoHelium in %, 0-100 (default 0) (null clears it)
oxygen_pctNoOxygen in %, 0-100 (whole numbers) (null clears it)
visibilityNoVisibility: High (Good (high)), Average, Low (Poor (low)) (null clears it)
water_typeNoWater: Salt (Salt water), Fresh (Fresh water) (null clears it)
dive_centerNoDive center or operator (free text) (null clears it)
weight_typeNoHow the weighting felt: Light (Too light), Good, Heavy (Too heavy) (null clears it)
end_pressureNoCylinder pressure at the end, in bar (metric) or psi (imperial) (null clears it)
nitrogen_pctNoNitrogen in %, 0-100 (default: the rest to 100) (null clears it)
body_of_waterNoBody of water: Ocean, Lake, Quarry, River, Other (null clears it)
cylinder_sizeNoCylinder size: litres of water volume (metric) or cubic feet (imperial, converted the way the PADI web app does) (null clears it)
cylinder_typeNoCylinder material: Steel, Aluminum (Aluminium), Other (null clears it)
adventure_diveNoAdventure dive (Advanced elective dives 7-9): Deep Diving, Underwater Navigation, Altitude Diving, Boat Diving, Digital Underwater Imaging, Drift Diving, Dry Suit Diving, Fish Identification, Night Diving, Peak Performance Buoyancy, Search and Recovery, Rescue, Underwater Naturalist, Wreck Diving, Adaptive Support Diver, Cavern Diving, Delayed Surface Marker Buoy Dive, Dive Against Debris Diver (AWARE), Diver Propulsion Vehicle (DPV), Enriched Air Diver, Full Face Mask Diver, Ice Diver, Rebreather Diver, Self-Reliant Diver, Shark Conservation Dive(AWARE), Sidemount Diver (null clears it)
start_pressureNoCylinder pressure at the start, in bar (metric) or psi (imperial) (null clears it)
bottom_time_minNoBottom time in whole minutes. Needed unless the dive is a Draft (null clears it)
bottom_water_tempNoWater temperature at depth, in C (metric) or F (imperial) (null clears it)
surface_water_tempNoWater temperature at the surface, in C (metric) or F (imperial) (null clears it)
visibility_distanceNoVisibility distance, in m (metric) or ft (imperial) (null clears it)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly=false, idempotent=true and destructive=false, and the description adds substantial behavior on top: partial-update semantics, the fact that null clears optional fields but cannot clear title/date/location/dive_type, the state-based lock on verified dives, the unit interpretation of every numeric field, and the return value. That is well beyond what the annotations provide.

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 mutation contract, then clearing rules, then units, then the lock condition, then the return value — a sensible escalation of detail. It is a little dense and the unit enumeration partially restates what individual schema properties already say, keeping it from a perfect score.

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?

For a 40-parameter mutation on a tool with no annotations gaps and no output schema, the description covers the three things an agent could actually get wrong: which fields mutate, how nulls behave, and which dive states reject the call. It also states the return value, so nothing material is left unaddressed.

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 schema already carries most per-field meaning and a 3 would be defensible. The description still earns above baseline by grouping all 40 parameters into a single unit convention (depth/visibility in m or ft, temperatures in C or F, weight in kg or lb, cylinder size in litres or cu ft, pressures in bar or psi, times in minutes) and by stating the null-clearing rule once instead of per field.

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?

"Change a dive in the PADI logbook" pairs a specific verb with a specific resource, and the following sentence pins down the patch semantics ("Only the fields you pass change"), which is exactly what separates this from logbook_create_dive. An agent can tell whether it wants create, update, or delete without opening a schema.

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?

It gives a clear condition for use (changing an existing dive), explicitly points to logbook_create_dive as the semantic reference for field values, and states that Pending/Verified/QR Code Verified dives are locked from both update and delete. It does not, however, mention logbook_get_dive for reading current values before a patch, so a small inference is left to the agent.

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