Standalone MCP server for food inventory and expiry reminders.
Moderate quality. All 8 tools have descriptions (10 - 200 chars, mostly good) and explicit input schemas with typed properties. Naming follows verb_noun pattern (add, list, update, mark, remove, check, set). However, several parameters lack descriptions or have vague ones. Output schemas are not documented. Error handling is minimal, no recovery guidance or actionable error messages. The tool set is well-composed (single responsibility per tool) and includes good domain logic (work cycles, reminder policies), but LLM-facing definitions need refinement.
Add a food item to the standalone Cyberboss food inventory. Use explicit dates when the user provides them. For unpackaged foods, the tool estimates a suggested use-by date from conservative food rules. If storage is ambiguous, such as raw meat without fridge/freezer context, the tool asks for clarification instead of guessing.
Check which food reminders are due, expired, or upcoming. Reminder timing respects the saved work cycle, so foods expiring during a 48-hour away window are surfaced before departure. Once an item is due, it remains due on every daily check through expiry and afterward until it is physically gone and removed; remind the user once per calendar day.
List food items from the standalone Cyberboss food inventory.
Mark a food item. If the food is physically gone, such as consumed, discarded, eaten, drunk, finished, or used up, remove it from inventory. If it still exists, including expired, overdue, spoiled, or still in the fridge, keep it active so reminders continue.
Permanently remove one food item by id. cyberboss_food_mark also removes whole consumed or discarded foods.
Output schemas not documented. Handlers return {text, data} but LLMs cannot infer what fields 'data' contains. For example, cyberboss_food_add returns result.item and result.count, but this structure is invisible to the agent.
Parameters with vague or missing descriptions. 'workCycle' and 'policy' in cyberboss_food_check_expiry accept additionalProperties: true but have no guidance on valid keys. 'status' in cyberboss_food_mark lacks enum constraint, LLMs may hallucinate invalid statuses.
No error handling guidance. Handlers do not return actionable error messages. If inventory.addFood() fails due to ambiguous storage, the response includes needsClarification but no guidance on what the LLM should do next (e.g., 'Ask the user for clarification').
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 55 | <=2025-11-25 | v2 |
Set reminder timing policy for food expiry checks.
Set the user's repeating away/home work cycle for food reminder timing. For a 48-hour shift pattern, pass awayHours 48, homeHours 48, and anchorAwayStart as the first known away start.
Update one food item by id. Use this to adjust dates, quantity, notes, storage, category, or status.
Missing parameter descriptions. 'storage' in cyberboss_food_list has description 'Optional storage filter' but does not specify valid values (fridge, freezer, pantry, etc.). 'category' in cyberboss_food_add lacks guidance on how to discover valid category IDs.
No pagination or result limits documented. cyberboss_food_list returns all items without limit or offset parameters. If inventory grows large, response could exhaust context window.