Skip to main content
Glama
MCP for PADI

MCP for PADI

by Mrc527

Log a dive

logbook_create_dive

Add a dive to a PADI logbook by recording title, date, location, type, depth, and time, plus optional details when provided; draft or publish it as appropriate.

Instructions

Add a dive to the user's PADI logbook. Required: title, date (YYYY-MM-DD, not in the future), location, dive_type, and, unless status is Draft, max_depth and bottom_time_min. Everything else is optional: leave out what the user did not say (or send null), never guess. 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. Values are PADI's exact words, listed in each field's description, for example dive_type Boat, BeachShore (shore and beach also work) or Other; status Publish (default) or Draft; gas Air, Enriched_32, Enriched_36, Enriched_40 (these fill the oxygen, nitrogen and helium percentages), or Enriched, Trimix, Rebreather with oxygen_pct, nitrogen_pct and helium_pct summing to 100. Training dives: give training {course, log_number, adventure_dive, skills}. Courses and log numbers: Open (Open Water, 1-4), Advanced (Advanced Open Water, 5 Deep, 6 Navigation, 7-9 elective dives that need adventure_dive), Rescue (10-11), DSD (Discover Scuba Diving, 12), Reactivate (13), SpecialtyAndDistinctive (no log number). Skills are PADI's values for the course (listed in training.skills): Open the flexible skills, Rescue the exercises, Reactivate the requirements. Training dives are saved as Draft; a PADI Pro must then verify them (logbook_submit_for_verification). Returns the saved 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": {
      "title": "<title>",
      "date": "<date>",
      "location": "<location>",
      "dive_type": "<dive_type>"
    },
    "name": "logbook_create_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
dateYesDive 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
notesNoNotes (free text)
surgeNoSurge: SomeSurge (Light surge), MediumSurge, BigSurge (Strong surge). "strong" means BigSurge; "none" means no surge
titleYesDive title, for example the site name. Training dives (except Specialty) get the PADI course title instead
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
statusNoPublish (a logged dive, the default) or Draft (incomplete: depth and time may be missing)
weightNoWeight carried, in kg (metric) or lb (imperial)
buddiesNoBuddies (one free-text field, for example "Sam, Kim")
currentNoCurrent: NoCurrent, SomeCurrent (Light current), MediumCurrent, StrongCurrent. "light" means SomeCurrent
feelingNoHow the dive felt: Amazing, Good, Average, Poor
time_inNoTime in, HH:MM (not verified with PADI yet; PADI's web app does not show it)
weatherNoWeather: Sunny, Partly Cloudy, Cloudy, Rainy, Windy, Foggy
air_tempNoAir temperature, in C (metric) or F (imperial)
locationYesDive site or place (free text; logbook_search_dive_sites lists PADI's site names)
time_outNoTime out, HH:MM (not verified with PADI yet; PADI's web app does not show it)
trainingNoOnly for training dives (saved as Draft; then use logbook_submit_for_verification)
dive_typeYesDive 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)
max_depthNoMaximum depth, in m (metric) or ft (imperial). Needed unless the dive is a Draft
helium_pctNoHelium in %, 0-100 (default 0)
oxygen_pctNoOxygen in %, 0-100 (whole numbers)
visibilityNoVisibility: High (Good (high)), Average, Low (Poor (low))
water_typeNoWater: Salt (Salt water), Fresh (Fresh water)
dive_centerNoDive center or operator (free text)
weight_typeNoHow the weighting felt: Light (Too light), Good, Heavy (Too heavy)
end_pressureNoCylinder pressure at the end, in bar (metric) or psi (imperial)
nitrogen_pctNoNitrogen in %, 0-100 (default: the rest to 100)
body_of_waterNoBody of water: Ocean, Lake, Quarry, River, Other
cylinder_sizeNoCylinder size: litres of water volume (metric) or cubic feet (imperial, converted the way the PADI web app does)
cylinder_typeNoCylinder material: Steel, Aluminum (Aluminium), Other
start_pressureNoCylinder pressure at the start, in bar (metric) or psi (imperial)
bottom_time_minNoBottom time in whole minutes. Needed unless the dive is a Draft
bottom_water_tempNoWater temperature at depth, in C (metric) or F (imperial)
surface_water_tempNoWater temperature at the surface, in C (metric) or F (imperial)
visibility_distanceNoVisibility distance, in m (metric) or ft (imperial)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the mutation profile (readOnlyHint false, destructiveHint false, idempotentHint false, openWorldHint false), so credit goes to what the description adds: training dives are forced to Draft and require a PADI Pro to verify, gas presets auto-fill oxygen/nitrogen/helium percentages, units govern both input and the response, and it returns the saved dive. It does not address duplicate submissions, though idempotentHint=false already signals that.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the required-field contract, which is the right ordering, but it is one dense block that re-enumerates values (dive_type, status, gas variants) already spelled out in each field's schema description. With 100% schema coverage those repeats cost space without adding meaning.

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 38-parameter creation tool with no output schema, the description covers the required set, the Draft exception, unit handling, the training sub-object and its course/log-number mapping, and the verification follow-up. An agent has everything needed to call it correctly without guessing.

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 earns more by adding cross-field semantics the schema can't express cleanly, such as which unit applies to each numeric family, how gas presets cascade into percentages, and the overall rule to omit rather than fabricate values. It does duplicate some per-field enum lists that already live in the schema.

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: 'Add a dive to the user's PADI logbook.' An agent immediately knows this creates a new logbook entry. It doesn't explicitly distinguish itself from the sibling logbook_update_dive, so an agent must infer that edits go elsewhere.

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?

Gives strong conditional guidance: which fields are required, that max_depth and bottom_time_min are only needed unless status is Draft, that everything else should be omitted or null and never guessed, and that training dives are saved as Draft and then flow to logbook_submit_for_verification. The one gap is that it never states when to use this versus logbook_update_dive.

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