Fitatu MCP Unofficial

Search Fitatu Food

search_food

Read-onlyIdempotent

Searches Fitatu product and recipe catalogs using one or more query variants, returning user and public results with optional measures and details.

Instructions

Searches Fitatu catalogs for products and recipes. The server does not infer brand or retailer aliases; provide alternative phrases together in queries when needed. Each query returns separate userItems and publicItems lists in Fitatu's order; the server does not merge or deduplicate candidates across those sources. Set includeDetails=true only when an alternative or missing measure is needed. A candidate has exactly one definition id: productId means use the PRODUCT meal-item variant; raw recipeId means use the RECIPE variant. Copy that id with a listed measureId. Do not send foodType.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`date`	No	Date context for Fitatu's authenticated user search. Defaults to today's local date.
`limit`	No	Maximum candidates per query per source. Defaults to 5.
`locale`	No	Fitatu search locale. Defaults to pl_PL.	pl_PL
`queries`	Yes	One or more independent food search phrases. When a description is ambiguous or may use a retailer, producer, or private-label name, submit plausible query variants together in one call. Results remain grouped by input query.
`detailsLimit`	No	Total number of top candidates per query to enrich with product or recipe details and measures across both source lists. User candidates consume the quota first. Use 0 to skip details.
`includeDetails`	No	Whether to fetch additional product or recipe information and available measures. Leave false when the candidate's default measure is sufficient; enable it when the default measure is missing or an alternative measure is needed. Defaults to false.
`includeUserFood`	No	Whether to use Fitatu's authenticated user search source. Its exact composition and ordering are determined by Fitatu.
`includePublicFood`	No	Whether to search Fitatu's public food catalog.

Output Schema

TableJSON Schema

Name	Required	Description
`results`	Yes	Search results grouped by input query, with separate user and public source lists.
`warnings`	No	Non-fatal warnings produced while searching or fetching details.
`queryCount`	Yes	Number of search queries processed by this call.
`resultCount`	Yes	Total number of returned user and public candidate items across all queries.
`warningDetails`	No	Structured details for non-fatal warnings.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 21, 2026

TDQS

A5/5.0

Behavior5/5

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

Annotations declare readOnlyHint and idempotentHint. The description adds crucial behavioral traits: no alias inference, separate userItems/publicItems lists not merged/deduplicated, candidate id semantics (productId vs recipeId), and constraint on foodType. Contradicts nothing.

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?

Four tightly packed sentences, all informative, front-loaded with the core search function and caveats. No fluff.

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?

Covers all behavioral caveats an agent needs: alias handling, result grouping, id selection, detail toggling, and forbidden fields. Output schema exists for return format; no gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds significant meaning beyond the schema: explains query variant grouping, details quota consumption order (user first), and candidate id usage. Enriches parameter understanding.

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 ('Searches'), resource ('Fitatu catalogs for products and recipes'), and explicitly contrasts with the sibling search_food_by_barcodes (barcode vs. phrase search). Clear differentiation.

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?

Explicitly instructs when to use includeDetails (only when alternative/missing measure needed), how to construct queries (provide alternative phrases together), and what not to send ('Do not send foodType'). Includes exclusions and alternatives.

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