Skip to main content
Glama
MCP for PADI

MCP for PADI

by Mrc527

Look up a PADI Pro

logbook_lookup_instructor
Read-onlyIdempotent

Look up a PADI Pro by member number to confirm the instructor's name before submitting a logbook verification request.

Instructions

Look up a PADI Pro (instructor or divemaster) by PADI member number and return the name. Use it to check a number with the user before logbook_submit_for_verification.

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": {
      "member_number": "<member_number>"
    },
    "name": "logbook_lookup_instructor"
  }
}

Input Schema

NameRequiredDescriptionDefault
member_numberYesThe PADI Pro's member number (digits only)

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 declare it read-only, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds the returned content ('return the name') and the pre-submission verification role, which is real context beyond the annotations. It does not say what happens when a member number is unknown, which is the main remaining gap.

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?

Two short sentences with the lookup behavior front-loaded and the workflow use case second. Nothing is redundant or padded.

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?

For a one-parameter lookup with no output schema, the description covers the input source, the returned field, and the workflow purpose, which is enough to call it correctly. Only the response for an invalid or unknown member number is left to inference.

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 coverage is 100% and the single parameter is fully documented in the schema, including the digits-only pattern. The description only restates that it is keyed by PADI member number, adding no format or validation detail beyond the schema, so the baseline of 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?

States a specific verb and resource ('Look up a PADI Pro'), names the accepted entity types (instructor or divemaster) and the keying parameter (PADI member number), and states the return value. An agent can distinguish this from sibling tools like logbook_submit_for_verification 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 Guidelines4/5

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

Gives explicit when-to-use guidance and names the sibling it feeds into: 'check a number with the user before logbook_submit_for_verification.' It doesn't state exclusions or what to do when the lookup fails, but the intended role in the workflow is unambiguous.

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