Skip to main content
Glama
Sign In
loseit-mcp

loseit-mcp

by cabird
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

delete_entry

Delete a food diary entry by providing its ID. The entry is moved to trash for recovery before permanent removal.

Instructions

Delete a diary entry. Get the entry_id from get_diary for the same day. A recoverable copy is written to local trash before deleting.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "entry_id": "<entry_id>"
    },
    "name": "delete_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoThe day the entry is on: 'YYYY-MM-DD', 'today', 'yesterday'.
entry_idYes`entry_id` from get_diary.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Discloses that a recoverable copy is written to local trash before deletion, revealing key behavioral trait not evident from annotations (none provided). This adds significant value for an AI agent.

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 with no waste. Action verb front-loaded. Every sentence earns its place.

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

Completeness5/5

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

Given only 2 parameters and presence of output schema, description sufficiently covers core behavior and undoability. No gaps for this delete action.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. Description adds value by specifying that entry_id comes from get_diary, which clarifies parameter usage beyond schema fields.

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 'Delete a diary entry' with a specific verb and resource. It distinguishes from siblings like get_diary (retrieval) and log_food (addition).

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?

Provides explicit instruction to obtain entry_id from get_diary, guiding correct usage. Does not explicitly state when not to use or provide alternatives, but context of deletion is straightforward.

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

Deploy Server

Other Tools