Retrieve all foods in a Mealie group. Use search, filtering, and pagination to explore or export your group's food list.
Get All [GET /api/explore/groups/{group_slug}/foods]
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | ||
| search | No | ||
| orderBy | No | ||
| perPage | No | ||
| group_slug | Yes | ||
| 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?
With no annotations, the description should disclose behavior. It only says 'Get All' without mentioning pagination, rate limits, permissions, or side effects. The schema has pagination params but no behavioral explanation.
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 under-specified. It is a single line lacking structure or additional helpful details for the agent.
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 9 parameters and no output schema, the description is grossly incomplete. It does not explain return format, pagination, filtering, or any usage context.
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?
Schema coverage is 0%, meaning no parameter descriptions. The description adds no meaning to the 9 parameters, failing to compensate for the lack of schema documentation.
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' combined with the endpoint indicates listing all foods for a group, but it is vague. It does not explicitly state it retrieves a list of foods or differentiate from the sibling 'explore_foods_get_one'.
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 versus siblings like 'explore_foods_get_one'. No mention of pagination, filtering, or context for using this list endpoint.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.