Skip to main content
Glama
Sign In
garmin-mcp

garmin-mcp

by sasha-sup
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Remote

garmin_weight

Read-onlyIdempotent

Retrieve daily weigh-in data such as weight, BMI, body fat, muscle mass, and body water over a chosen date range to track body composition trends.

Instructions

Daily weigh-ins: weight (kg), BMI, body fat, muscle mass, body water where available. Range up to 2 years, default last 90 days.

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

Input Schema

NameRequiredDescriptionDefault
daysNoNumber of days ending at end_date, used when start_date is omitted.
end_dateNoLast day, YYYY-MM-DD. Default: today.
start_dateNoFirst day, YYYY-MM-DD in the user's local calendar. Default: computed from end_date and days.

Output Schema

NameRequiredDescriptionDefault
toYes
fromYes
entriesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true. The description adds the default 90-day window, the 2-year maximum range, and that some metrics are only present 'where available', which is meaningful beyond the annotations, but it does not cover pagination, rate limits, or response behavior.

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 compact sentence that front-loads the returned metrics and follows with range/default behavior. Every clause contributes useful information with no wasted wording.

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 read-only data retrieval tool with annotations and an output schema, the description covers the key metrics, default range, maximum range, and availability caveat. It lacks explicit routing guidance versus sibling tools, but is otherwise sufficient for correct invocation.

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%, so the schema already documents days, end_date, and start_date well. The description adds the 2-year maximum range constraint, which is not in the schema, but otherwise defers to the schema for parameter meaning.

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 clearly identifies the resource and metrics: daily weigh-ins including weight, BMI, body fat, muscle mass, and body water. It is specific about the data returned, though it does not explicitly differentiate from nearby siblings like garmin_daily_summary or garmin_body_battery.

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 description gives useful default behavior (last 90 days) and a maximum range (2 years), which implicitly tells the agent how to query. It does not state when to prefer this tool over alternatives or any exclusions, so guidance is present but incomplete.

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