Skip to main content
Glama
MCP for PADI

MCP for PADI

by Mrc527

Set logbook units

logbook_set_units
Idempotent

Set the PADI logbook display units to metric or imperial without changing stored dive data; when the server uses logbook settings, its answers switch to match.

Instructions

Set the units the PADI logbook shows on learning.padi.com: metric or imperial. PADI always stores metric values, so no dive changes. When this server follows the logbook setting (units auto), its answers switch too.

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": {
      "units": "<units>"
    },
    "name": "logbook_set_units"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitsYesmetric (m, C, bar, kg, litres) or imperial (ft, F, psi, lb, cubic feet)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already state destructiveHint=false and idempotentHint=true; the description adds genuinely new behavior: PADI always stores metric so no dive records change, and the server's own answers may switch if it follows the logbook setting. That is exactly the kind of consequence disclosure a mutation tool benefits from. It does not mention auth or whether the setting is per-account or per-browser, which keeps it from a 5.

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?

Three short sentences, front-loaded with the action and the allowed values, then the storage caveat and the server-wide side effect. No filler or redundant restatement of the title.

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?

A one-parameter mutation with no output schema is essentially fully covered: what changes, what does not change, and the knock-on effect on server answers are all stated. Only minor operational details (persistence scope, auth needs) are absent, which is acceptable at this complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and the enum parameter already documents metric (m, C, bar, kg, litres) vs imperial (ft, F, psi, lb, cubic feet). The description repeats the two value names but adds no format or default information beyond the schema, so the baseline 3 applies.

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?

Specific verb plus resource plus scope: 'Set the units the PADI logbook shows on learning.padi.com: metric or imperial.' The two allowable values are stated inline, and no sibling tool touches units, so the 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 Guidelines4/5

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

The description makes clear this is a display-layer setting and even explains the follow-on condition: when the server runs in 'units auto' mode, its answers switch as well. It stops short of any explicit when-to-call/when-not guidance or prerequisites (e.g., whether a login or logbook is required), so it is clear context rather than full routing guidance.

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