Skip to main content
Glama

search_foods

Read-only

Search Garmin's full food catalog, including FatSecret and custom foods, to find branded or generic items by name and retrieve food IDs, sources, servings, and macros for logging.

Instructions

Search Garmin's general food catalog (FatSecret + Garmin custom foods)

    Searches across the entire food catalog including FatSecret-sourced
    branded and generic foods, not just the user's Garmin custom foods.
    Use this to find branded packaged foods by name before logging them.

    Returns food_id, source, name, brand, and all available servings with
    macros. The source field ("FATSECRET" or "GARMIN") and food_id together
    identify the right routing for log_custom_food — pass both to
    log_custom_food's food_id and source parameters respectively.

    For the user's own custom foods only, use get_custom_foods instead.

    Args:
        query: Food name or brand to search for (e.g. "Cheerios", "Greek yogurt")
        start: Starting index for pagination (default 0)
        limit: Maximum number of results per page (default 20)
    

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": {
      "query": "<query>"
    },
    "name": "search_foods"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
startNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint and non-destructive behavior, so safety is covered; the description adds real value on top by disclosing the returned fields (food_id, source, name, brand, servings with macros) and how the source enum routes to log_custom_food. It does not mention pagination limits or rate/catalog size constraints, which would be needed for a 5.

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?

Front-loaded with the purpose and scope in the first two lines, then returns, then routing, then the alternative. Slightly verbose with the indented Args block that partly re-serializes the schema, but that duplication is justified given 0% schema description coverage.

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

Completeness5/5

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

No output schema exists, and the description compensates by enumerating the returned fields and their meaning. Return values will be parsed, routing to log_custom_food is explained, and the sibling alternative is named — nothing an agent needs to call this correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden and does so: it documents query with concrete examples, start as a pagination index, and limit as results per page with defaults. It stops short of stating the maximum page size or the effect of large offsets.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Search Garmin's general food catalog') and declares its scope precisely — the entire catalog including FatSecret-sourced foods, not just the user's custom foods. It is clearly distinguishable from get_custom_foods, which it names explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit when-to-use ('find branded packaged foods by name before logging them'), an explicit when-not-to-use with the correct alternative ('For the user's own custom foods only, use get_custom_foods instead'), and even the downstream routing to log_custom_food via the food_id/source pair.

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