Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CYBERBOSS_FOOD_STORE_FILENoThe path to the food inventory JSON file. Defaults to ./data/food-inventory.json if not set.

Capabilities

Features and capabilities supported by this server

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
cyberboss_food_addA

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 }

cyberboss_food_listC

List food items from the standalone Cyberboss food inventory. Input: { storage?: string, status?: string, includeClosed?: boolean }

cyberboss_food_updateB

Update one food item by id. Use this to adjust dates, quantity, notes, storage, category, or status. Input: { id: string, name?: string, quantity?: string, storage?: string, category?: string, bestBeforeDate?: string, expiresAt?: string, notes?: string, status?: string }

cyberboss_food_markA

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. Input: { id: string, status: string, notes?: string }

cyberboss_food_removeA

Permanently remove one food item by id. cyberboss_food_mark also removes whole consumed or discarded foods. Input: { id: string }

cyberboss_food_check_expiryA

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. Input: { now?: string, includeAll?: boolean, workCycle?: {}, policy?: {} }

cyberboss_food_set_work_cycleA

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. Input: { type?: string, awayHours: number, homeHours: number, anchorAwayStart: string }

cyberboss_food_set_reminder_policyB

Set reminder timing policy for food expiry checks. Input: { normalLeadHours?: number, beforeDepartureBufferHours?: number, afterReturnGraceHours?: number }

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
Cyberboss Food Tool IndexStandalone food inventory tools and schemas.

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