Skip to main content
Glama
MCP for PADI

MCP for PADI

by Mrc527

Dive statistics

logbook_stats
Read-onlyIdempotent

Calculate PADI logbook statistics: dive count, total and average bottom time, deepest and longest dives, first/last dates; filter by date range or group by year, month, location, or dive type.

Instructions

Statistics of the PADI logbook: number of dives, total bottom time (minutes and h:mm), the deepest and the longest dive, average maximum depth and bottom time, first and last dive date. Optional date range (from/to, YYYY-MM-DD, inclusive) and grouping: none (default), year, month, location, dive_type or log_type. Depth in m or ft (see units).

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_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoOnly dives on or before this date (YYYY-MM-DD)
fromNoOnly dives on or after this date (YYYY-MM-DD)
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.
group_byNoAlso give the numbers per year, month, location, dive type or log type (default none)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety needs no restating. The description adds real behavior beyond that: the inclusive from/to semantics, the default grouping of none, the unit resolution rule, and the exact set of metrics returned — which matters because there is no output schema.

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 metric list, then the two behavioral clauses (range, grouping). Dense with no filler, though the first sentence is a long comma-separated run that is slightly harder to scan than separate bullets would be.

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

Completeness4/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 carries the return-shape burden and does so by listing every reported metric plus the unit and grouping behavior. It stops short of showing how grouped results are structured (per-group rows vs nested) or how the h:mm format is returned, a minor remaining gap for an aggregate tool.

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%, and the description still adds meaning: it states that from/to are inclusive, which the schema does not say, and frames group_by as 'also give the numbers per ...' clarifying that grouping augments rather than replaces the totals. Units are deferred to the schema, which is appropriate.

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?

Names a specific resource (PADI logbook) and enumerates exactly what is computed: dive count, total bottom time, deepest/longest dive, averages, first/last date. This is clearly an aggregate tool and distinguishable from list_dives or get_dive siblings without opening any schema.

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

Usage Guidelines3/5

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

Usage is implied through the optional date range and grouping parameters, so an agent can infer 'use this to summarize a period or dimension.' However, no sibling is named and there is no explicit when-not guidance (e.g., use logbook_get_dive for a single dive), leaving the agent to infer the boundary itself.

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