Skip to main content
Glama

Tally food nutrients

Search foods

search_foods
Read-onlyIdempotent

Find foods by name in the ANSES-CIQUAL 2020 table (3,167 foods, names in English). Returns ids to pass to get_food_nutrients.

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
limitNoHow many results. Default 8.
queryYesA food name in English, e.g. "lentils", "salmon", "oat".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive behavior, so the safety profile is covered. The description adds genuinely useful context beyond that: the corpus is a fixed 2020 table of 3,167 English-named foods, and the output is identifiers for a follow-up call rather than nutrient data. It does not discuss result ranking or what happens on ambiguous matches.

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?

Two short sentences, front-loaded with what the tool searches and immediately followed by the handoff to the sibling tool. Nothing is redundant or padded.

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?

For a two-parameter search tool with full schema coverage and complete annotations, the description supplies everything an agent needs: the corpus, the language constraint, and the downstream usage of the returned ids. No output schema exists but the return value's purpose is stated.

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%, with both query (English food name, with examples) and limit (1-20, default 8) documented in the schema itself. The description repeats the English-name constraint but adds no semantics the schema lacks, so the baseline 3 applies.

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 (find), resource (foods by name), named data source (ANSES-CIQUAL 2020, 3,167 foods) and the naming constraint (English). It also says the tool returns ids rather than nutrients, which cleanly separates it from get_food_nutrients.

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

Usage Guidelines4/5

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

The description gives clear workflow guidance by saying the returned ids are to be passed to get_food_nutrients, and warns that names must be in English. It does not say when not to use it or what to do when a name yields no match, so it stays short of full when/when-not coverage.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources