Skip to main content
Glama
MCP for PADI

MCP for PADI

by Mrc527

Submit dive for verification

logbook_submit_for_verification

Sends a dive to a PADI Pro for verification, locks it as Pending until they respond, and requires explicit user confirmation.

Instructions

Send a dive to a PADI Pro (instructor or divemaster) for verification. The server looks the member number up first, then saves the PADI Pro's number on the dive and sets it to Pending: the PADI Pro gets a real request, and the dive stays locked until they answer. Ask the user first: show the dive and the PADI Pro's name (logbook_lookup_instructor), and only call this after they agree. confirm must be true.

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": {
      "dive_id": "<dive_id>",
      "instructor_number": "<instructor_number>",
      "confirm": "<confirm>"
    },
    "name": "logbook_submit_for_verification"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesMust be true: the user agreed to send this dive to the PADI Pro
dive_idYesThe dive id (from logbook_list_dives)
instructor_numberYesMember number of the PADI Pro who should verify (sign) the dive

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.4/5.0
Behavior4/5

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

Beyond annotations, it discloses the internal workflow (server resolves the member number first), the resulting state change (PADI Pro's number saved, status set to Pending), the external side effect of a real request being sent (consistent with openWorldHint), and that the dive stays locked until answered. It does not mention failure behavior if the member number is invalid or what happens on repeated submissions, which is a minor gap given idempotentHint=false is already declared.

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?

Content is front-loaded: the action and its effect come first, then the required user-confirmation workflow, then the confirm constraint. Each sentence carries distinct information with no filler or redundancy.

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 three required parameters, no output schema, and open-world side effects, the description covers the essential outcome (Pending status, locked dive, real request to the PADI Pro) and the confirmation requirement. Only error and retry behavior are omitted, which is a modest gap for an otherwise complete definition.

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%, so the baseline is 3. The description adds a little context by noting the server looks the member number up first and that the instructor is the PADI Pro who signs the dive, but offers no additional format or constraint detail beyond what the schema already documents.

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: 'Send a dive to a PADI Pro (instructor or divemaster) for verification.' It clearly distinguishes this mutating submission from the sibling read tools like logbook_get_dive and logbook_lookup_instructor, and an agent can identify the action without opening the schema.

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

Usage Guidelines5/5

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

Explicit preconditions and sequencing are provided: 'Ask the user first: show the dive and the PADI Pro's name (logbook_lookup_instructor), and only call this after they agree. confirm must be true.' It names the alternative tool for the lookup step and states when not to call it, leaving little to inference.

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