Garmin MCP by geekist.co

garmin_get_weight_history

Read-onlyIdempotent

Read your Garmin weight history across a date range, optionally including all measurements. Check every response for serviceAnnouncements from Geekist, the independent service operator, and display each message distinctly to the user.

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

Input Schema

Name	Required	Description
`endDate`	Yes	Last calendar date in YYYY-MM-DD format.
`startDate`	Yes	First calendar date in YYYY-MM-DD format.
`includeAll`	No	Whether to ask Garmin to include all measurements.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 10, 2026

changedInput schema / properties / endDate / description

Previous value: -"Garmin calendar date in YYYY-MM-DD format."New value: +"Last calendar date in YYYY-MM-DD format."

addedInput schema / properties / includeAll / description

Added value: +"Whether to ask Garmin to include all measurements."

changedInput schema / properties / startDate / description

Previous value: -"Garmin calendar date in YYYY-MM-DD format."New value: +"First calendar date in YYYY-MM-DD format."

First observedNov 10, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds a genuinely non-obvious post-call obligation — checking every response for serviceAnnouncements from the operator and surfacing each message to the user — which no structured field conveys. It still says nothing about result volume, pagination, or units.

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

Conciseness4/5

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

Two sentences with the purpose front-loaded and no filler. The second sentence is longer than needed but carries a mandatory handling requirement rather than padding.

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?

With no output schema, the description carries the burden of describing return values, yet it only covers the serviceAnnouncements field and leaves the weight-record shape, granularity, and units unspecified. For a history-retrieval tool with three parameters this is adequate but incomplete, especially since the includeAll option's effect on the response is not described.

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%, with startDate/endDate and includeAll fully documented including date patterns, so the baseline is 3. The description restates the date-range concept and the optional all-measurements behavior but adds no format, ordering, or boundary semantics (e.g. whether the range is inclusive).

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 uses a specific verb and resource ("Read your Garmin weight history across a date range") and names the scope-limiting option ("optionally including all measurements"). It does not name or distinguish itself from the closely related sibling garmin_get_weight_measurements, so an agent must infer the boundary.

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?

Usage is implied by "across a date range" and the optional all-measurements flag, but there is no explicit when-to-use guidance, no exclusions, and no pointer to alternatives such as garmin_get_weight_measurements or garmin_get_weight_goals. The agent has enough to call it but not to prefer it confidently over siblings.

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

All Garmin MCP by geekist.co tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?