Skip to main content
Glama
MCP for PADI

MCP for PADI

by Mrc527

Get dive photos

logbook_get_photos
Read-onlyIdempotent

Retrieve photos attached to a specific PADI logbook dive, returning up to a chosen limit while skipping oversized or unsupported image formats.

Instructions

Get the photos attached to a dive in the PADI logbook, as images (at most max, 1-5, default 3). Very large photos, and photos in a format AI apps cannot show (for example HEIC), are left out and counted as skipped.

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>"
    },
    "name": "logbook_get_photos"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxNoMost photos to return, 1-5 (default 3)
dive_idYesThe dive id (from logbook_list_dives)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world profile, so safety is covered. The description nonetheless adds real behavioral value the annotations do not: output is capped at max (default 3), and oversized images or formats AI apps cannot render (e.g. HEIC) are silently omitted and counted as skipped — a non-obvious partial-result semantic. It stops short of saying where that skipped count appears or how the images are encoded.

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?

Two tight sentences, with the core action front-loaded before the truncation/skip caveat. Slight redundancy in repeating the max range and default that the schema already carries, but no filler or vague wording.

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 two-parameter read tool with full schema coverage and no output schema, the description covers what it returns (images), the cap, and the important failure mode (skipped photos). Its only gap is not clarifying where the skipped count surfaces in the result, which matters since no output schema documents the response shape.

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%, including the max bounds (1-5, default 3) and the dive_id provenance from logbook_list_dives, so the baseline is 3. The description restates the max cap and default but adds no new meaning such as ordering of returned photos or whether max counts skipped items.

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 names a specific verb and resource — retrieve the photos attached to a dive in the PADI logbook — and states the return medium (images). It is easy to separate from logbook_get_dive, which returns dive data rather than photos, though the description never names that sibling explicitly.

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 implied rather than stated: an agent can infer this is the tool for fetching photos once it has a dive id. There is no explicit when-to-use-versus-alternative guidance, no mention that logbook_get_dive should be called first for metadata, and no stated prerequisites beyond the schema's dive_id reference.

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