Skip to main content
Glama

search_foods

Read-only

Search the FatSecret catalog to find a food's loggable servings, calories, and macros, using an English rendering for non-English input.

Instructions

Find catalog Foods with loggable Servings, kcal and Macros.

Search one food at a time. Search a composed dish, such as a plate in a photo, as a whole first (e.g. "beef bibimbap"), and its components separately only when the dish has no good match. Pass the User's original description and, for non-English input, an English rendering: the catalog is searched with the English rendering, or the original when omitted. Nutrition and metric amounts describe the whole Serving; number_of_units is its FatSecret unit count. A not_found result is normal. When a branded product isn't among the matches, ask the User for a photo of its Nutrition Label and draft it as a Stand-in with draft_entries. This tool does not write to the Food Diary.

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

Input Schema

NameRequiredDescriptionDefault
descriptionYesThe description of one food as the User said it.
english_renderingNoEnglish rendering for the catalog. Pass this for non-English input.

Output Schema

NameRequiredDescriptionDefault
statusYes
matchesYes
attributionNoPowered by fatsecret Platform API

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.6/5.0
Behavior4/5

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

Adds real behavior beyond the readOnlyHint annotation: results are searched via the English rendering, a not_found result is expected rather than an error, and nutrition/metric amounts describe the whole Serving while number_of_units is the FatSecret unit count. The closing 'does not write to the Food Diary' largely restates readOnlyHint=true, and no result-count or ranking behavior is described.

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?

Purpose is front-loaded in the first line and every subsequent sentence carries a distinct rule (one-at-a-time, dish decomposition, language handling, not_found, branded fallback). It is dense but not padded; the only near-redundant sentence is the Food Diary disclaimer.

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?

An output schema exists, so return values needn't be explained, and the description still covers the semantics an agent needs to call it correctly: input wording, language handling, the single-food constraint, and the escalation path for branded products. Nothing material is missing for a two-parameter read-only search.

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 coverage is 100%, so the baseline is 3, but the description goes further by specifying the priority rule: the catalog is searched with the English rendering, or the original when it is omitted. It also clarifies that 'description' should be the user's own wording, which the schema only hints at.

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 ('Find catalog Foods') plus scope detail ('loggable Servings, kcal and Macros'), which tells the agent exactly what kind of object comes back. It also implicitly separates itself from draft_entries, the sibling it points to for branded products.

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 explicit operating rules: one food at a time, search composed dishes whole before components, pass the user's original wording plus an English rendering, and treat not_found as normal. It names the alternative path (ask for a Nutrition Label photo, draft with draft_entries) and the condition that triggers it.

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