Skip to main content
Glama

garmin_food_search

Read-only

Search Garmin or custom food records and return each serving's ID and macros so you can select the right entry for food logging.

Instructions

Search foods, with each serving's id and macros (what garmin_log_food needs).

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

Input Schema

NameRequiredDescriptionDefault
limitNo1-50
queryNoFood name to search for
startNoOffset, from 0
sourceNocatalog = Garmin/FatSecret foods; custom = your owncatalog

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuine value by disclosing the shape of each result (serving id + macros), which matters because there is no output schema. It says nothing about pagination behavior or result ordering, so it stops short of rich behavioral context.

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?

A single front-loaded sentence with no wasted words, and the parenthetical is high-value rather than filler. It is arguably too terse for a search tool with four parameters, but nothing in the text is redundant.

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 no output schema, the description partly compensates by naming the returned fields, and annotations cover the read-only profile. Gaps remain around result ordering, the distinction between catalog and custom results, and the follow-up workflow, so it is adequate rather than complete for a four-parameter search tool.

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 100% and the enum for source is documented inline, so the schema carries all parameter meaning. The description adds no extra semantics about query matching (partial vs exact) or how start/limit paginate, which is the baseline-3 outcome.

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?

"Search foods" gives a specific verb+resource, and the parenthetical clarifies what each result contains (serving id and macros). It clearly distinguishes itself from write-side siblings by flagging that its output feeds garmin_log_food, though it doesn't distinguish itself from other nutrition lookups like garmin_nutrition or garmin_save_custom_food.

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 phrase "what garmin_log_food needs" implicitly positions this as the lookup step before logging a food, which is useful routing. However, there is no explicit when-to-use/when-not guidance and no mention of the related custom-food save flow or the nutrition summary sibling, so the agent must infer the workflow.

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