Skip to main content
Glama

cyberboss_food_remove

Permanently remove a food item from inventory by providing its ID. This tool deletes the entry directly without affecting consumption records.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
Behavior3/5

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

Describes action as 'permanently remove', implying destructive behavior, but lacks details on permissions, reversibility, or error handling. With no annotations, this is adequate but not thorough.

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

Conciseness5/5

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

Two sentences, no wasted words, front-loaded with core action. Efficient and clear.

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 no output schema and simple input, the description sufficiently covers the removal action. Lacks return value info but acceptable for a straightforward deletion.

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 has 1 parameter (id) with 0% description coverage. Description only repeats 'id' as a string, adding no semantic value or context beyond the schema.

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 the tool removes one food item by id, and distinguishes from sibling tool cyberboss_food_mark which removes whole consumed/discarded foods.

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?

Mentions alternative tool (cyberboss_food_mark) that also removes items, providing implicit guidance on when to use each. Could explicitly state when to use this tool.

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