Skip to main content
Glama

get_daily_weigh_ins

Retrieve all weigh-in entries for a specific date to track daily weight changes.

Instructions

Get all weigh-in entries for a specific date

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoDate in YYYY-MM-DD format. Defaults to today if not provided

Implementation Reference

  • Tool 'get_daily_weigh_ins' is registered via registerTool on the MCP server, with input schema from dateParamSchema, description 'Get all weigh-in entries for a specific date'. Calls client.getDailyWeighIns(date).
    server.registerTool(
      'get_daily_weigh_ins',
      {
        description: 'Get all weigh-in entries for a specific date',
        inputSchema: dateParamSchema.shape,
      },
      async ({ date }) => {
        const data = await client.getDailyWeighIns(date);
        return {
          content: [{ type: 'text' as const, text: JSON.stringify(data, null, 2) }],
        };
      },
    );
  • Handler async function that destructures {date} from arguments, calls client.getDailyWeighIns(date), and returns the result as JSON text content.
    async ({ date }) => {
      const data = await client.getDailyWeighIns(date);
      return {
        content: [{ type: 'text' as const, text: JSON.stringify(data, null, 2) }],
      };
    },
  • GarminClient.getDailyWeighIns method: resolves date (defaults to today), makes an HTTP GET request to WEIGHT_DAY_VIEW_ENDPOINT with the date and ?includeAll=true query parameter.
    async getDailyWeighIns(date?: string): Promise<unknown> {
      const resolvedDate = date ?? todayString();
      return this.request(`${WEIGHT_DAY_VIEW_ENDPOINT}/${resolvedDate}?includeAll=true`);
    }
  • dateParamSchema: Zod schema with an optional 'date' field (YYYY-MM-DD format, defaults to today). Used as inputSchema for get_daily_weigh_ins.
    export const dateParamSchema = z.object({
      date: dateString
        .optional()
        .describe('Date in YYYY-MM-DD format. Defaults to today if not provided'),
    });
  • WEIGHT_DAY_VIEW_ENDPOINT constant: '/weight-service/weight/dayview' — the Garmin API endpoint used by getDailyWeighIns.
    export const WEIGHT_DAY_VIEW_ENDPOINT = '/weight-service/weight/dayview';
Behavior2/5

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

With no annotations, the description must disclose behavioral traits, but it only states the basic function. It does not mention return format (e.g., array) or behavior for missing dates or timezone handling.

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?

Single sentence, 9 words, front-loaded with verb and resource. No wasted words.

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?

Given the tool's simplicity (one optional parameter) and absence of output schema, the description is minimally adequate. However, it lacks differentiation from similar tools and doesn't clarify what fields the weigh-in entries contain.

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?

The schema already fully describes the parameter with a regex and default. The description adds no additional meaning beyond what is in the schema, so a baseline score of 3 is appropriate.

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 states it retrieves weigh-in entries for a specific date, which differentiates it from sibling tools like 'get_weigh_ins' and 'get_latest_weight' by implying the daily filter. However, it does not explicitly distinguish from 'get_weigh_ins'.

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?

No guidance is provided on when to use this tool versus alternatives such as 'get_weigh_ins' for a range or 'get_latest_weight'. The agent receives no usage context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Nicolasvegam/garmin-connect-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server