Skip to main content
Glama
MCP for PADI

MCP for PADI

by Mrc527

Search dive sites

logbook_search_dive_sites
Read-onlyIdempotent

Search PADI dive site names by partial text match to suggest a location for a dive. Sites not found in the list can still be saved as free text.

Instructions

Search PADI's list of dive site names (case-insensitive text match). Use it to suggest a location for a dive. A location that is not in the list can still be saved as free text.

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": {
      "query": "<query>"
    },
    "name": "logbook_search_dive_sites"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMost sites to return, 1-50 (default 20)
queryYesPart of a dive site name

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?

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: matching is case-insensitive and substring-based, and a miss is not a dead end because free text is allowed. It stops short of describing result shape or ordering, so it adds some but not rich context.

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, front-loaded with the core behavior and immediately followed by the practical implication for callers. No filler, no restatement of the tool name, and the fallback note earns its place.

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 simple two-parameter read tool with full annotation coverage, the description covers what is needed to call it correctly. The one gap is that with no output schema, the agent is not told what a result contains (name only, or an identifier usable when setting a site on a dive), which matters for the stated follow-up use case.

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%, and the schema already documents both parameters including the partial-name semantics ('Part of a dive site name') and the 1-50 limit range with the default of 20. The description adds only the case-insensitivity note, which is marginal. Baseline 3 is correct when the schema does the heavy lifting.

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: search PADI's list of dive site names, with the matching semantics (case-insensitive text match) spelled out. This is unmistakably different from the dive-record siblings (create/get/list) since it operates on a site-name catalog, not on logbook entries.

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 an explicit intended use ('suggest a location for a dive') and a fallback rule for the negative case ('A location that is not in the list can still be saved as free text'), which prevents the agent from blocking on a miss. It does not name a competing tool or state exclusions, but no sibling offers an overlapping search, so the guidance is sufficient.

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