Skip to main content
Glama
Sign In
Garmin MCP Server

Garmin MCP Server

by nitinmms
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_weight

Read-only

Retrieve daily latest weights and body composition for a date range, with weights in grams and a range average for trend analysis.

Instructions

Get weight and body composition for a date range: daily latest weights and range average.

Weights are in grams.

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": {
      "start_date": "<start_date>"
    },
    "name": "get_weight"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_dateNo
start_dateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

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 and openWorldHint=true, so safety is covered. The description adds genuinely useful context beyond that — the output shape (daily latest values plus a range average) and the unit (grams). It says nothing about pagination, missing-data days, or how body composition is aggregated.

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?

Two short sentences, front-loaded with purpose and scope, followed by a unit clarification that could not be inferred elsewhere. Nothing is wasted.

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 simple two-parameter read tool with no output schema, the description covers purpose, aggregation behavior, and units. The remaining gaps — date format and the meaning of an omitted end_date — are minor but real for an agent constructing the call.

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 the load. It conveys that the parameters form a date range, but not the date format, nor what happens when the optional end_date is omitted (single day? through today?). Only partial compensation for the coverage gap.

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 specific verb and resource ('Get weight and body composition') plus the scope ('for a date range') and what is returned ('daily latest weights and range average'). It is clearly distinct from siblings like get_weight_goals, though it never names an alternative explicitly.

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 only implied: the required date range signals a historical-range query, and 'daily latest weights' hints at per-day granularity. There is no statement of when to prefer this over get_weight_goals or any exclusion/prerequisite.

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