Garmin MCP Lite

Overview Schema Source Related Servers Discussions Admin

garmin_dive_logs

Retrieve freediving and scuba dive logs with depth, bottom time, water temperature, and dive reflex heart rate metrics; fetch recent dives or details for a specific activity ID.

Instructions

Get freediving and scuba diving logs and metrics (depth, bottom time, water temperature, dive reflex HR).

Args: limit: Number of recent dive activities to return (default: 5, max: 20). activity_id: Specific dive activity ID to fetch details for (optional).

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": "garmin_dive_logs"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`activity_id`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.1.10Nov 9, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are supplied, so the description carries the burden. 'Get' plus the listed metrics makes the read-only nature and return contents reasonably evident, and an output schema exists so return shape need not be spelled out. It says nothing about permissions, rate limits, or what happens when activity_id refers to a non-dive activity.

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?

One purpose sentence plus a tight Args block; front-loaded and free of filler. The docstring-style argument listing is slightly redundant with the schema but still reads cleanly.

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?

A simple two-parameter read tool with an output schema; purpose, both params, and a bound not present in the schema are all covered. Only minor gaps remain around the interaction between the two params and authentication expectations.

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?

Schema description coverage is 0%, so the description must compensate, and it does: it gives the default (5) and, critically, the max (20) for limit, which the schema does not state, and clarifies that activity_id fetches details for a specific dive. It does not say whether limit is ignored when activity_id is set, which is the main remaining ambiguity.

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?

Names a specific verb ('Get') and a precise resource ('freediving and scuba diving logs') with the returned metric categories enumerated. That is specific enough to separate it from the generic garmin_activities / garmin_activity_detail siblings without opening their schemas, though it never states that boundary 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 by the two params: 'limit' for a recent-list view and 'activity_id' for one dive's detail. There is no explicit when-to-use versus garmin_activities or garmin_activity_detail, and no statement of when this tool is the wrong choice.

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