Skip to main content
Glama

Expiry Tracker storage guide

Get a food's storage times

get_storage_guide
Read-onlyIdempotent

Returns how long one food keeps in the fridge, freezer and pantry, for each state the guide lists (unopened, opened, cooked, ...), with the best way to store it, spoilage signs, freezing and thawing, myths, advice for people at higher risk, common questions, sources and the page URL. Pass a slug from search_foods, or a food name.

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": {
      "food": "<food>"
    },
    "name": "get_storage_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
foodYesA slug from search_foods (for example 'yogurt') or a food name.
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.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (read-only, idempotent, closed-world, non-destructive), so the description's job is to say what comes back, and it does so thoroughly: storage times per state, storage method, spoilage signs, freezing/thawing, myths, high-risk advice, FAQs, sources and page URL. The only minor omission is the failure behavior when a slug is not found.

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 dense sentence with no filler, but it front-loads the return payload and pushes the one action-critical instruction ('pass a slug...') to the end, burying the call prerequisite.

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?

There is no output schema, so the description carries the burden of describing return content and does so item by item. Combined with annotations covering safety and a fully documented two-parameter schema, an agent has everything needed to call it correctly.

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%, so both parameters are already documented, including the language enum and its default. The description only restates the food parameter's accepted forms without adding format or fallback details, which is the baseline case.

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?

Names a specific verb and resource — returns how long one food keeps in fridge, freezer and pantry — and enumerates the returned sections, which clearly distinguishes it from the search_foods lookup sibling.

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?

Tells the agent the acceptable input ('pass a slug from search_foods, or a food name'), which establishes the two-step search-then-fetch workflow. It does not state when not to call it or that it should follow search_foods rather than be called speculatively, so it falls short of a full when/when-not treatment.

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