Retrieve a paginated list of foods from Mealie with optional search, ordering, and filtering. Use it to fetch foods matching criteria for recipe management integration.
Get All [GET /api/foods]
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | ||
| search | No | ||
| orderBy | No | ||
| perPage | No | ||
| queryFilter | No | ||
| orderDirection | No | desc | |
| paginationSeed | No | ||
| orderByNullPosition | No |
Changes observed during successful MCP inspections.
v0.2.11Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided and description lacks any behavioral details (e.g., pagination, filtering, read-only nature). Agent cannot infer side effects or constraints.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Extremely concise but at the expense of utility. Does not front-load key information; the single line 'Get All' is insufficient for an 8-parameter tool.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the lack of annotations, output schema, and parameter descriptions, the tool definition is severely incomplete. The agent has no way to properly invoke this tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With 0% schema description coverage and no parameter details in the description, the agent has no understanding of what parameters like 'search', 'orderBy', 'page', etc., mean or how to use them.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Get All' is vague and does not specify the resource being retrieved. Although the tool name and endpoint imply foods, the description itself fails to state the purpose clearly.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool over siblings like 'explore_foods_get_all'. No differentiation or context provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.