Skip to main content
Glama

get_weigh_ins

Read-only

Retrieve weight measurements between a start and end date to track body weight trends in Garmin Connect. Dates use YYYY-MM-DD format.

Instructions

Get weight measurements between specified dates

    Args:
        start_date: Start date in YYYY-MM-DD format
        end_date: End date in YYYY-MM-DD format
    

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>",
      "end_date": "<end_date>"
    },
    "name": "get_weigh_ins"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_dateYes
start_dateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/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 safety profile is covered structurally. The description adds nothing beyond the operation itself: no mention of ordering, pagination or result limits on long ranges, timezone handling for date boundaries, or whether dates are inclusive. For an open-world read tool, these are the gaps that matter.

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?

The purpose sentence is short and front-loaded, and the Args block is functional rather than padding. The docstring-style indentation and restated parameter names are slightly redundant, but the format hint justifies the second block.

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 simple two-parameter read with annotations covering safety and no output schema to document, this is close to adequate. What is missing is range semantics (inclusivity, ordering) and any notion of result volume, which an agent needs to call it correctly with wide date spans.

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 carries the burden, and it does supply the YYYY-MM-DD format for both dates, which the schema does not. It still omits whether the range is inclusive at both ends, whether order matters (start before end), and timezone assumptions.

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 measurements between specified dates'. An agent can tell this is a range query over weigh-in records. It does not, however, distinguish itself from the sibling get_daily_weigh_ins, which an agent could easily confuse with it.

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?

The only usage signal is the implied one that this tool takes a date range. There is no statement of when to prefer it over get_daily_weigh_ins or other weigh-in reads, no exclusions, and no prerequisites such as authentication or data availability.

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