Skip to main content
Glama
Sign In
garmin-mcp-server

garmin-mcp-server

by JohanBellander
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_personal_records

Retrieve personal records across all activities from Garmin Connect. Get fastest times, longest distances, and other personal bests to monitor your progress.

Instructions

Get personal records (PRs) across all activities. Returns fastest times, longest distances, and other personal bests.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description is the only behavioral signal. It does disclose what the tool returns (fastest times, longest distances, other bests) and that it spans all activities, which is helpful; however it does not mention any caveats around data freshness, computation scope, or limitations beyond that.

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 pithy sentences convey purpose, scope, and return content with no redundancy. The definition is front-loaded and every clause 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 zero-argument read-only tool with an output schema present, the description covers purpose, scope, and return content. It could slightly strengthen completeness by specifying whether PRs are all-time versus date-range filtered, but nothing essential is missing for safe invocation.

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?

There are no parameters and schema coverage is 100%, so the description has no parameter burden. The baseline for a zero-parameter tool is 4, and the description appropriately focuses on the return value instead.

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 names a specific resource (personal records/PRs), scopes it across all activities, and illustrates the output with fastest times and longest distances. This distinguishes it from sibling metrics like get_endurance_score or get_race_predictions.

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?

The intended use is implied: call it whenever an agent needs a user's personal bests for any activity. It does not explicitly contrast with alternatives or state when not to use it, so it falls at the solid/implied level.

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

Deploy Server

Other Tools