Skip to main content
Glama
Sign In
garmin-mcp

garmin-mcp

by konstantintutsch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_weigh_ins

Read-only

Retrieve Garmin Connect weigh-in records for a specified date range using YYYY-MM-DD start and end dates. Query body weight history for tracking and analysis without modifying account data.

Instructions

Get weigh-ins between startdate and enddate using format 'YYYY-MM-DD'. (Garmin Connect, read-only. Dates are YYYY-MM-DD.)

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": {
      "startdate": "<startdate>",
      "enddate": "<enddate>"
    },
    "name": "get_weigh_ins"
  }
}

Input Schema

NameRequiredDescriptionDefault
enddateYes
startdateYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/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 'read-only' note in the description is redundant. The description does add the date-format constraint, but says nothing about results per day, ordering, or pagination.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Very short and front-loaded, but the date format is stated twice ('using format YYYY-MM-DD' and 'Dates are YYYY-MM-DD'), so part of the text does not earn its place.

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?

An output schema exists so return values need no explanation, and annotations cover safety. Still, for a range-query tool the description leaves open inclusive/exclusive boundaries and result granularity, which an agent would want before calling.

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 0%, so the description must carry parameter meaning. It supplies the required 'YYYY-MM-DD' format for both dates, which is genuinely useful, but it does not state whether enddate is inclusive, whether times/timezones matter, or any other constraint.

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?

States a clear verb and resource: retrieve weigh-ins between startdate and enddate from Garmin Connect. It does not explicitly distinguish itself from siblings like get_body_composition or get_stats_and_body, which also cover body metrics, so it stops short of a 5.

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?

There is no when-to-use guidance and no mention of alternatives. An agent has to infer from the name alone whether weigh-ins belong here or in get_body_composition / get_stats_and_body, which overlap in body-weight territory.

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