Skip to main content
Glama

get_daily_weigh_ins

Read-only

Fetch weight measurements for a given date from Garmin Connect to track daily weigh-ins and monitor weight changes.

Instructions

Get weight measurements for a specific date

    Args:
        date: 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": {
      "date": "<date>"
    },
    "name": "get_daily_weigh_ins"
  }
}

Input Schema

NameRequiredDescriptionDefault
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. The description adds nothing beyond that: it does not say what is returned when no weigh-in exists for the date, whether multiple measurements per day are possible, or what units are used.

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 single-sentence summary is front-loaded and wastes no words. The 'Args:' docstring boilerplate is slightly redundant given the one-parameter schema, but it carries the format detail that makes it worthwhile.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description bears the burden of describing the return value, yet it only says 'weight measurements' without indicating units, list vs. single value, or empty-result behavior. For a lookup tool with zero schema coverage, this leaves the agent guessing at what comes back.

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% — the schema only gives a bare string named 'date' with title 'Date'. The description usefully supplies the required YYYY-MM-DD format, which is real added meaning, but says nothing about timezone interpretation or whether the date is local or UTC.

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 with a scope qualifier: 'Get weight measurements for a specific date.' An agent can tell this is a single-date read, but the description never contrasts it with the sibling get_weigh_ins, so the boundary between the two is left implicit.

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 or when-not-to-use guidance and no mention of alternatives such as get_weigh_ins for a broader range. The only hint is the phrase 'specific date,' which implies but never states the selection condition.

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