Skip to main content
Glama
MCP for PADI

MCP for PADI

by Mrc527

PADI account info

padi_account_info
Read-onlyIdempotent

Retrieve connected PADI account details, logbook units, read-only status, API mode, server date and version. Set check to test PADI connectivity and count dives.

Instructions

Show the connected PADI account (name, e-mail, PADI affiliate id), the units (the server setting and the PADI logbook setting), whether the account is read-only, the API mode, whether it is a demo account, the server's date (today, in time_zone; the user's own date can differ by a day) and the server version. With check=true it also tests the connection to PADI and counts the dives; it then answers even when the PADI sign-in fails (connected false, the error in check). check also tries the same reads, read-only, on PADI's other logbook address (check.otherApi), to see whether it would work too; the server keeps using its own.

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": "padi_account_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
checkNoAlso test the connection to PADI and count the dives

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the read-only and idempotent annotations, the description discloses important behavior: check counts dives, still returns a response when PADI sign-in fails (connected false with the error in check), and additionally probes PADI's other logbook address via check.otherApi while noting the server keeps using its own. It also warns that the server date can differ from the user's local date by a day.

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 dense and front-loads the account information it returns, with no obvious filler. Its single run-on sentence lists many fields and behaviors, which slightly reduces readability, but every clause contributes relevant information.

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 only one optional parameter, no output schema, and rich read-only annotations, the description provides everything needed: what is returned, how check alters behavior, failure semantics, and the alternate API probe. No significant aspect of the tool's behavior is left unexplained.

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?

The single check parameter is fully described in the schema, but the description adds substantial meaning: it tests the PADI connection, counts dives, tolerates sign-in failure, and exercises the alternate logbook API in check.otherApi. This goes well beyond the schema's brief parameter note.

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?

The description uses a specific verb ('Show') and enumerates the exact resources returned: PADI account name, e-mail, affiliate id, units, read-only status, API mode, demo flag, server date, and server version. This makes the tool's purpose unmistakable and clearly distinct from logbook-oriented siblings, although it does not explicitly name alternatives.

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?

The description explains what check=true does, which is useful parameter usage context, but it does not explicitly state when to call this tool versus alternatives or when not to use it. Usage is implied by the account-information scope rather than directly guided.

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