Skip to main content
Glama
Nutrition MCP
by ronkommoji

search_food_history

Search previously logged meals by raw text or parsed food item names, with optional date range and result limit filters, to review past eating habits and calorie intake.

Instructions

Search previous logged meals by raw text or parsed food item names.

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_food_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
endDateNoOptional YYYY-MM-DD end date.
startDateNoOptional YYYY-MM-DD start date.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden. It implies a read-only search but says nothing about result ordering, pagination, match behavior (fuzzy vs exact), or what a hit looks like, leaving the agent to guess at anything beyond the barest operation.

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 tight sentence with the core filtering semantics front-loaded and no filler. Its brevity is efficient rather than padded, though one more clause on scope would have been cheap.

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?

For a 4-parameter read-only search with no output schema, the definition conveys the essential matching surface and enough to invoke it correctly. What it omits, return shape, ordering, and limit behavior, are extras rather than blockers.

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?

The phrase 'raw text or parsed food item names' genuinely adds meaning about query semantics that the schema does not capture. Against that, 'limit' is undocumented in both places and the date parameters only carry schema-level explanations, so at 50% coverage the description compensates only partially.

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

Purpose4/5

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

States a specific verb (search) and a specific resource (previously logged meals) with the matching surface (raw text or parsed food item names). It is distinguishable from log_food and the summary tools, but never names a sibling or clarifies boundaries against them.

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

Usage Guidelines3/5

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

'Previous logged meals' implies the historical-lookup context, so an agent can infer when to reach for it. However, there is no explicit when-to-use framing, no exclusions (e.g., use get_daily_status for aggregates), and no mention of alternatives among the siblings.

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