Skip to main content
Glama

Expiry Tracker storage guide

Search the storage guide

search_foods
Read-onlyIdempotent

Finds foods in the storage guide for a food word or a product name in Turkish, English, German, Spanish, French, Italian, Russian, Japanese or Arabic (for example 'yoğurt', 'opened milk', 'Kaşar peyniri', 'Hähnchenbrust'). Returns up to 8 foods with their slug, a one-line summary and the page URL. Use the slug with get_storage_guide.

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
queryYesA food or product name, a few words at most.
languageNoLanguage of the answer: tr, en, de, es, fr, it, ru, ja or ar. Defaults to the language the food was found in.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral detail: a hard result cap of 8 and the exact return shape (slug, one-line summary, page URL). It does not describe ranking or empty-result behavior, keeping it short of 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences: capability and accepted languages first, return shape second, next-step routing last. No redundant restatement of the title or name, and every sentence contributes information an agent needs before calling.

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?

With no output schema, the description correctly carries the return-value burden by naming the three returned fields and the 8-item cap, and it covers the language dimension and follow-up tool. Minor gap: no mention of what happens when nothing matches or how results are ordered, which matters for a search tool.

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; the description earns above that by illustrating the query parameter with real multilingual strings, showing that multi-word native-language phrases like 'Kaşar peyniri' or 'opened milk' are valid input, which the schema's terse 'a food or product name, a few words at most' does not convey.

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 ('Finds foods in the storage guide') plus the accepted input form (food word or product name) across nine named languages, with concrete example queries. It also distinguishes itself from the sibling by positioning get_storage_guide as a follow-up detail lookup rather than a search.

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?

Explicitly routes the agent: 'Use the slug with get_storage_guide' tells it this is the discovery step and names the alternative for full detail. It lacks an explicit when-not-to-use condition (e.g., exact slug already known, or no results), but the workflow guidance is clear.

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