Skip to main content
Glama

delete_meal_item

Remove a specific meal entry from your nutrition log by providing its item ID. This action helps maintain accurate food tracking records in your personal fitness database.

Instructions

Delete a meal item.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
item_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Implementation of the delete_meal_item MCP tool, which removes a record from the meal_items table in the database.
    @app.tool()
    def delete_meal_item(item_id: int) -> dict[str, bool]:
        """Delete a meal item."""
        conn = get_connection()
        cursor = conn.cursor()
        cursor.execute("DELETE FROM meal_items WHERE id = ?", (item_id,))
        conn.commit()
        conn.close()
        return {"deleted": cursor.rowcount > 0}
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Delete' implies a destructive mutation, but the description doesn't mention whether this operation is reversible, what permissions are required, what happens to associated data, or what the output contains. This leaves critical behavioral aspects unspecified for a destructive tool.

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?

The description is extremely concise at just four words, with zero wasted language. It's front-loaded with the core action and resource, making it easy to parse quickly. Every word earns its place in conveying the essential purpose.

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

Completeness3/5

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

Given that this is a destructive tool with no annotations and 0% schema description coverage, but with an output schema present, the description is minimally adequate. The output schema will provide return value information, but the description still lacks crucial context about behavioral implications, parameter meaning, and differentiation from sibling tools.

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?

The input schema has 0% description coverage, with one required parameter 'item_id' of type integer. The description adds no semantic information about what 'item_id' represents, how to obtain it, or its format. For a tool with no schema descriptions, the description fails to compensate by explaining the parameter's meaning or usage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Delete') and the resource ('a meal item'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'delete_meal' or 'delete_nutrition_day', which would require specifying what distinguishes a 'meal item' from those other entities.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. With siblings like 'delete_meal', 'upsert_meal', and 'add_or_update_meal_item', there's no indication of the relationship between these tools or when deletion of a meal item is appropriate versus deletion of an entire meal.

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/JohnZolton/MCP-logger'

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