Skip to main content
Glama
sedoglia

Garmin Connect MCP Server

by sedoglia

find_similar_activities

Search for activities matching a given activity's type, distance, and duration within 20% tolerance, returning the closest matches with full metrics and similarity scores.

Instructions

Find activities similar to a reference activity by type, distance and duration (within 20% tolerance). Returns the closest matches first, each with its full metrics and a similarity score.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of similar activities to return (default: 10)
activityIdYesReference activity ID (required)
searchDepthNoHow many recent activities to search through (default: 200)
Behavior4/5

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

The description discloses key behaviors: tolerance (20%), sorting by closeness, and return of full metrics with similarity scores. Without annotations, this provides adequate transparency for an AI agent to understand the tool's effects.

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 sentences, each adding distinct value: the first states purpose and criteria, the second describes output. No redundant or unnecessary information.

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?

The description covers the tool's purpose, matching criteria, tolerance, sorting, and output format. While there is no output schema, the description compensates. It is complete for a tool of this complexity.

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%, so baseline is 3. The description adds context about matching criteria (type, distance, duration, tolerance) but does not elaborate on individual parameters beyond the schema descriptions.

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 clearly states the tool's function: finding activities similar to a reference activity based on type, distance, and duration. This is a specific verb-resource combination and distinguishes itself from sibling tools, as no other tool performs similarity matching.

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?

The description implicitly guides when to use the tool (to find similar activities) but does not explicitly contrast with alternatives like direct filtering. However, the purpose is clear enough to infer appropriate usage.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sedoglia/garmin-mcp-ts'

If you have feedback or need assistance with the MCP directory API, please join our Discord server