Skip to main content
Glama

cyberboss_food_update

Update food item details including dates, quantity, storage, category, notes, or status by ID.

Instructions

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 }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
nameNo
notesNo
statusNo
storageNo
categoryNo
quantityNo
expiresAtNo
bestBeforeDateNo
Behavior2/5

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

No annotations provided, so description bears full burden. Does not disclose whether update is partial or full, what happens to omitted fields, idempotency, permissions, or side effects. Assumed to be a patch-like update but not explicitly stated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Concise with two sentences and a pseudo-schema, but the 'Input' block is redundant with the actual schema, wasting space. Could be shorter by omitting the Input block.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 9 optional parameters, no output schema, and no annotations, the description is minimal. Lacks information on return value, error handling, or behavior when fields are omitted. Inadequate for a mutation tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, yet description merely restates parameter names with types (identical to schema). No added semantic details like format constraints, allowed values, or relationships between parameters.

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?

Clearly states tool updates one food item by ID and lists specific adjustable fields (dates, quantity, notes, storage, category, status). Differentiates from sibling tools like 'add' and 'remove' by focusing on modification.

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

Usage Guidelines3/5

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

Provides a usage hint ('Use this to adjust...') but lacks explicit guidance on when not to use it or alternatives (e.g., 'use cyberboss_food_add for new items'). Sibling names provide some context, but description doesn't leverage them.

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