Skip to main content
Glama
Sign In
garminconnect-js

garminconnect-js

by DynamicsNinja
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_nutrition_daily_meals

Read-only

Retrieve all meals logged for a specific calendar date in Garmin Connect, using the date (YYYY-MM-DD, UTC) to return daily nutrition entries.

Instructions

Meals logged on one date. GETs /nutrition-service/meals/{cdate}.

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": {
      "cdate": "<cdate>"
    },
    "name": "get_nutrition_daily_meals"
  }
}

Input Schema

NameRequiredDescriptionDefault
cdateYesCalendar date, YYYY-MM-DD (UTC)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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 and openWorldHint=true, and the description only restates that by quoting the GET endpoint path. It adds no behavioral context such as return shape, whether an empty day returns an empty list, or timezone handling beyond the schema's UTC note.

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?

Two short sentences with the purpose front-loaded. The endpoint-path sentence is low-value implementation detail but does not bloat the definition.

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 single-parameter read tool with annotations and full schema coverage, this is minimally viable. The missing piece is differentiation from get_nutrition_daily_food_log, which matters given how many nutrition siblings exist.

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 coverage is 100% and the single cdate parameter is fully documented (type, format, YYYY-MM-DD UTC). The description implies the date scoping but adds no meaning beyond the schema, so the baseline 3 applies.

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 resource and scope: meals logged on one date. An agent knows it returns meal data for a single day. However, it does nothing to separate itself from the close sibling get_nutrition_daily_food_log, so the agent cannot tell which to pick from the description alone.

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 when-to-use guidance, no exclusions, and no mention of the adjacent nutrition siblings (get_nutrition_daily_food_log, get_nutrition_food_log_range, get_nutrition_daily_settings). The agent must infer selection from the name.

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