Skip to main content
Glama
MCP for PADI

MCP for PADI

by Mrc527

Export dives

logbook_export_dives
Read-onlyIdempotent

Export PADI logbook dives as CSV or JSON, oldest first, filtered by date range; large logs return in parts using offset and next_offset.

Instructions

Export the dives of the PADI logbook (all, or a date range), oldest first, with every field, as CSV (for a spreadsheet) or JSON (for a backup). Large logbooks come in parts: at most limit dives per answer (default 50 for json, 100 for csv, up to 500); call again with offset=next_offset for the next part. The answer has two parts: a JSON summary (format, total, count, offset, next_offset, units), then the file content as text. Values are in the units of the summary.

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": {
      "format": "<format>"
    },
    "name": "logbook_export_dives"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoOnly dives on or before this date (YYYY-MM-DD)
fromNoOnly dives on or after this date (YYYY-MM-DD)
limitNoDives in this part, 1-500 (default 50 for json, 100 for csv). Large logbooks come in parts
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.
formatYescsv (a table, one row per dive) or json (a list of full dives)
offsetNoDives to skip, oldest first (use next_offset of the previous part)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.4/5.0
Behavior5/5

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

Well beyond the annotations, which already declare readOnly/idempotent/non-destructive: the description discloses ordering (oldest first), the batching model with per-format default page sizes, and the unusual two-part answer shape ("a JSON summary ... then the file content as text"). It also explains that numeric values follow the units reported in the summary, which is the kind of cross-field behavior an agent cannot infer elsewhere.

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?

Front-loaded with the purpose, then scope, then the batching constraint, then the return shape — the exact order an agent needs them. Every sentence carries a distinct operational fact; nothing is padding or restatement of the title.

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?

With no output schema, the description takes on the return-value burden and does so explicitly: a JSON summary (format, total, count, offset, next_offset, units) followed by file text. Combined with pagination, ordering, and unit semantics, an agent has everything needed to call it correctly and to continue a partial export.

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 one extra by tying limit and offset together into a pagination loop and stating the default page sizes in-context. It largely restates what the schema already documents per-field (from/to, units, format), so it does not add field-level syntax the schema lacks.

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?

Opens with a specific verb and resource plus scope: "Export the dives of the PADI logbook (all, or a date range), oldest first, with every field" and names the two output encodings. The bulk-export-with-every-field framing implicitly separates it from a paged list tool, but no sibling is named, so differentiation is inferential rather than explicit.

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 concrete selection guidance between the two formats ("CSV (for a spreadsheet) or JSON (for a backup)") and a clear instruction for the multi-part case: "call again with offset=next_offset for the next part." It does not name any alternative tool or state when not to use this one, so it stops short of explicit routing.

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