Garmin MCP for macOS

Overview Schema Source Related Servers Discussions Admin

garmin_api_food_logs

Read-only

Retrieve Garmin Connect food logs with optional meal, nutrition, goals, and media filters for a single date or up to a 31-day range.

Instructions

Food logs with optional goals, nutrition, media and meal filters. Raw JSON fields are not normalized. Date ranges default to 7 days and allow at most 31 days (activity search uses pagination).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "garmin_api_food_logs"
  }
}

Input Schema

Name	Required	Description	Default
`date`	No
`meal_id`	No
`include_goals`	No
`include_media`	No
`include_nutrition`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Oct 26, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint, so the safety profile is covered. The description adds valuable behavioral context beyond annotations: raw JSON fields are not normalized, date ranges default to 7 days and cap at 31 days, and a note that activity search uses pagination.

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 description is three compact sentences and front-loads the resource and filters. The parenthetical about activity search pagination is slightly tangential 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?

With an output schema and rich annotations, the description need not explain return values or safety. However, for a 5-parameter tool with 0% schema coverage, it should more fully specify filter parameters and date format to make invocation unambiguous.

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 compensate. It maps conceptual filters—goals, nutrition, media, meal filters, and date ranges—but does not explain exact parameter names, date format, meal_id meaning, or boolean defaults, leaving clear gaps.

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 identifies the resource as food logs with optional goals, nutrition, media, and meal filters. It does not use a precise verb like fetch/list and does not explicitly contrast with sibling tools, but the resource is distinct enough to distinguish it from activity, sleep, hydration, and other Garmin siblings.

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?

The date range default and maximum constraint provides some usage context, but the description does not explicitly state when to use this tool instead of alternatives. Usage is implied by the food-log resource, with no exclusions or named alternatives.

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