Skip to main content
Glama
garmin-personal-api-mcp

garmin-personal-api-mcp

by aaronhaddad

Food log

garmin_get_nutrition
Read-onlyIdempotent

Retrieves the foods and macros logged in Garmin Connect's nutrition log for a specified day, so you can review daily intake.

Instructions

Foods and macros logged in Garmin Connect's nutrition log for one day.

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_get_nutrition"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoDate as YYYY-MM-DD, or "today", "yesterday", "N days ago" (local time)today

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the description need not repeat safety properties. It adds only that results are scoped to one day's logged entries; it says nothing about whether unlogged days return empty results or how entries are grouped (meals vs totals).

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?

One sentence with no waste, resource and time scope front-loaded. Nothing redundant with the schema or annotations.

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

Completeness4/5

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

For a single-parameter, annotation-backed read tool with a fully described schema, the definition is largely sufficient. The only real gap is that no output schema exists and the description does not hint at the shape of the returned food/macro data.

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 date parameter is documented with format and relative-date forms, so the description carries no additional burden. Baseline 3 is appropriate here.

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 (Garmin Connect nutrition log) and a verb-like scope (foods and macros logged for one day). It reads clearly against siblings like garmin_get_hydration or garmin_get_weight, though it never explicitly distinguishes itself from them.

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 intent is implied by name and description — retrieve nutrition entries for a single day — but there is no explicit statement of when to use this versus, say, garmin_get_daily_summaries or garmin_get_hydration, and no exclusions or prerequisites.

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