Skip to main content
Glama
MCP for PADI

MCP for PADI

by Mrc527

List dives

logbook_list_dives
Read-onlyIdempotent

List and filter a user's PADI logbook dives by date, type, status, or search text; sort by date, depth, or bottom time and paginate results with unit options.

Instructions

List the dives of the user's PADI logbook, newest first (sort=max_depth: deepest first, sort=bottom_time: longest first). Returns {total, dives, next_offset, units}; each dive has its id (the dive_id of the other tools), title, date, location, type, status, depth and bottom time, and locked=true when it cannot be changed. Filters: log_type (Recreational or Training) or status (Draft, Publish, Pending, Resubmit, Verified, QR Code Verified), a date range (from/to, YYYY-MM-DD, inclusive) and query (text in the title, location or buddies). Use offset=next_offset for the next page. Depth is in m or ft (see units), bottom time in minutes. Dives without a depth or time come last when sorted by them. Use logbook_get_dive for every detail of one dive.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "logbook_list_dives"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoOnly dives on or before this date (YYYY-MM-DD)
fromNoOnly dives on or after this date (YYYY-MM-DD)
sortNoOrder, always descending: date (newest first, default), max_depth (deepest first) or bottom_time (longest first)
limitNoDives per page, 1-100 (default 15)
queryNoOnly dives with this text in the title, location or buddies
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.
offsetNoDives to skip (use next_offset of the previous page)
statusNoOnly dives with this status: Draft, Publish (Logged), Pending (Waiting for verification), Resubmit (Sent back by the PADI Pro), Verified, QR Code Verified (Verified with a QR code)
log_typeNoOnly these dives: Recreational, Training

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?

The annotations already declare a safe, idempotent read operation, and the description adds substantial behavioral context beyond them. It documents the response envelope, per-dive fields, the locked flag, unit-dependent values, sort behavior for missing depth or time, and pagination.

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?

The description is appropriately sized for a 9-parameter list tool and is front-loaded with the core purpose and ordering. It is dense and could be easier to scan with structured bullets, but no sentence is plainly wasteful.

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?

There is no output schema, so the description carries the burden of explaining return values, and it does: total, dives, next_offset, units, and the useful per-dive fields. Given the filters, pagination, units, and sibling tool, it is complete enough for an agent to invoke correctly.

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, but the description adds operational meaning: sort direction, inclusive date filtering, query scope across title/location/buddies, and using next_offset as the next page offset. Some parameter details are still repeated from the schema rather than expanded further.

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 and resource: listing the dives of the user's PADI logbook. It names the default ordering, supported sorting, and distinguishes the tool from logbook_get_dive for single-dive detail, so an agent can select it confidently.

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?

It explains when to use this list tool for browsing or filtering dives and explicitly routes single-dive detail requests to logbook_get_dive. Pagination guidance is also concrete: use offset=next_offset for the next page.

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