Skip to main content
Glama
MCP for PADI

MCP for PADI

by Mrc527

List certifications

padi_list_certifications
Read-onlyIdempotent

List your PADI certifications and eCards with titles, certification dates, PADI numbers, instructors, dive shops, and available card image links.

Instructions

List the user's PADI certifications (eCards): title, certification date, PADI number, instructor, dive shop and a link to the card image when PADI has one.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior3/5

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

The supplied annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety and side-effect profile is fully covered without the description's help. What the description adds beyond that is modest but real: it discloses which fields come back and signals a conditional return with "when PADI has one," warning the agent that the card image link may be absent. It does not mention auth requirements, empty-list behavior, or freshness of the cached data, which keeps this at a 3 rather than higher.

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?

A single sentence that front-loads the verb and resource, then lists return fields in a compact parenthetical. There is no filler, no restatement of the title, and every clause carries information the structured fields do not.

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?

There is no output schema, so the description carries the return-value burden, and it does so by naming each field, including the conditional card image link. For a zero-parameter read tool with full annotation coverage this is close to complete; only the absence of any note on authentication or the empty-list case leaves a small gap.

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?

With zero input parameters the baseline is 4, and the description correctly spends no words on argument syntax. It does implicitly scope the call to "the user's" own certifications with no filtering options, which usefully tells an agent that no user identifier can be passed.

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 opens with a specific verb and resource ("List the user's PADI certifications") and immediately clarifies what a certification record is by aliasing it to "eCards." It then enumerates the exact fields returned (title, date, PADI number, instructor, dive shop, card image link), so an agent knows precisely the shape of the domain object and can distinguish this from the logbook_* siblings, which deal with dives rather than certifications.

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 reasonably implied: this is the only certification-reading tool among the siblings, so an agent asking "what certifications does this user hold" will land here naturally. However, the description never states that explicitly, nor does it route the agent elsewhere for adjacent data such as account details (padi_account_info exists as a sibling). A brief "use this for credentials, use padi_account_info for profile/account data" would have earned a 5.

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