Skip to main content
Glama
Sign In
garmin-mcp

garmin-mcp

by konstantintutsch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_lactate_threshold

Read-only

Retrieve running lactate threshold data, including heart rate, power, and speed, from Garmin Connect for a date range or the latest reading.

Instructions

Return running lactate threshold information, including heart rate, power, and speed. (Garmin Connect, read-only. Dates are YYYY-MM-DD.)

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_lactate_threshold"
  }
}

Input Schema

NameRequiredDescriptionDefault
latestNo
end_dateNo
start_dateNo
aggregationNodaily

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds useful domain context ('Garmin Connect') and date format guidance, but does not explain aggregation behavior, pagination, or how 'latest' interacts with date bounds.

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?

The description is a single front-loaded sentence plus a short parenthetical, with no redundant or wasted text. The core purpose is stated first.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Although an output schema exists and annotations cover safety, the input schema has four undocumented parameters at 0% coverage. The description is not complete enough to tell an agent how to use 'latest', date ranges, and 'aggregation' correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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, but it only clarifies that dates are YYYY-MM-DD. It does not explain 'latest', the relationship between 'start_date' and 'end_date', or what values 'aggregation' accepts.

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 uses a specific verb and resource: 'Return running lactate threshold information,' and names the returned metrics (heart rate, power, speed). This clearly distinguishes it from sibling tools such as get_cycling_ftp or get_max_metrics.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the tool is for retrieving lactate threshold data but gives no explicit guidance on when to use it instead of related metric tools. It also does not explain when to use the 'latest' flag versus a date range, leaving selection to inference.

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