Skip to main content
Glama

cyberboss_food_add

Add food items to your inventory with automatic best-before estimates for unpackaged foods and storage clarification when needed.

Instructions

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. Input: { name: string, quantity?: string, storage?: string, category?: string, addedAt?: string, bestBeforeDate?: string, expiresAt?: string, expiresInDays?: number, notes?: string }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesFood name, such as spinach, chicken breast, or frozen beef.
notesNo
addedAtNoOptional add time/date. Defaults to now.
storageNoOptional storage: fridge, freezer, pantry, cold storage, frozen, or room temperature.
categoryNoOptional rule category id when known.
quantityNoOptional natural-language amount. Discrete counts such as 4 bottles or 4瓶 create one inventory item per unit.
expiresAtNoOptional exact expiry datetime.
expiresInDaysNoOptional number of days from addedAt.
bestBeforeDateNoOptional YYYY-MM-DD suggested use-by date.
Behavior3/5

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

No annotations are provided, so the description carries full burden. It discloses estimation of use-by dates and clarification behavior. However, it does not mention authentication, rate limits, idempotency, or what happens on duplicate names. The description is adequate but not exhaustive.

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?

The description is a single paragraph that efficiently conveys the tool's purpose and key behaviors. It is not verbose and front-loads the primary action. Minor improvements could include bullet points for parameters.

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?

Given the tool's complexity (9 parameters, no output schema), the description covers the essential behavior: adding an item, handling dates, and storage ambiguity. It is sufficiently complete for an add operation, though it could mention what happens on duplicate names or validation errors.

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?

Schema coverage is 89%, so the schema already documents most parameters. The description adds context about estimation and clarification, which hints at behaviors related to bestBeforeDate and storage parameters. It does not add deep semantic meaning beyond what the schema provides.

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?

The description clearly states 'Add a food item to the standalone Cyberboss food inventory.' It uses a specific verb and resource, and it naturally distinguishes from sibling tools like list, update, or remove.

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

Usage Guidelines4/5

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

The description provides usage guidance such as using explicit dates when provided, estimation for unpackaged foods, and clarification for ambiguous storage. It does not explicitly state when not to use this tool, but it gives clear context for its operation.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/caroliny1031/food-core'

If you have feedback or need assistance with the MCP directory API, please join our Discord server