Skip to main content
Glama
Sign In
garmin-mcp

garmin-mcp

by konstantintutsch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

garmin_call

Read-only

Execute a read-only Garmin Connect data method by name to retrieve health and activity data, including sleep, heart rate, stress, and training metrics, without modifying your account.

Instructions

Run any read-only Garmin Connect data method by name (see garmin_list_methods).

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": {
      "method": "<method>"
    },
    "name": "garmin_call"
  }
}

Input Schema

NameRequiredDescriptionDefault
methodYesMethod name from garmin_list_methods
argumentsNoKeyword arguments for the method

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false; the description reinforces the read-only nature and the dependency on garmin_list_methods. It does not describe error behavior for invalid methods, output variability, or how argument handling works beyond the schema.

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 definition is a single, front-loaded sentence with zero waste. It references the discovery tool immediately and adds no redundant explanation.

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

Completeness3/5

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

For a generic dispatcher with an output schema and safety annotations, the description is adequate but incomplete. It still leaves ambiguity about when to choose this tool over garmin_api_get or the specific getters, and the generic arguments parameter remains underspecified.

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 itself documents that 'method' comes from garmin_list_methods and that 'arguments' are keyword arguments. The description adds little beyond repeating that the method is named and comes from the list, which is baseline-appropriate for high schema coverage.

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?

The description states a specific action, 'Run any read-only Garmin Connect data method by name,' and points to garmin_list_methods for discovery. However, it does not distinguish this generic dispatcher from close siblings like garmin_api_get or the many specific getter tools.

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?

It gives some contextual guidance by saying the tool is for read-only Garmin Connect methods and refers the agent to garmin_list_methods. But it does not explain when to use this generic call instead of garmin_api_get or a specific sibling getter, and it states no exclusions.

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