Skip to main content
Glama
Life Admin MCP

Life Admin MCP

by NKC27

Delete item

delete_item
Destructive

Stop tracking an item by moving it to the trash, where it can be restored later; confirm with the user before proceeding.

Instructions

Stop tracking an item. It moves to the trash and can be brought back with restore_item. Confirm with the user first.

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": {
      "item": "<item>"
    },
    "name": "delete_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemYesThe item's exact title

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, so the safety bar is lower, and the description still adds real value: the operation is reversible (trash, restorable via restore_item) and should be confirmed with the user beforehand. It does not cover failure behavior for a non-existent or ambiguous title, which keeps it short of a 5.

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?

Three short sentences, front-loaded with the action and immediately followed by reversibility and the confirmation requirement. Nothing is redundant with the title alone.

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?

For a one-parameter soft-delete tool with annotations covering the destructive profile, the description covers action, reversibility, and the confirmation step. Only edge-case behavior (item not found, duplicate titles) is unaddressed, which is a minor gap.

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

Parameters3/5

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

Schema coverage is 100% and the single parameter is already documented as "The item's exact title," so the schema carries the burden. The description adds no extra meaning about matching behavior or what happens with duplicate titles; baseline 3 applies.

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?

"Stop tracking an item" states a specific action on a specific resource, and "moves to the trash" makes the soft-delete semantics explicit rather than leaving the agent to guess from the name. Naming restore_item as the inverse distinguishes it cleanly from that sibling.

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?

It supplies a workflow prerequisite ("Confirm with the user first") and a recovery path via restore_item, which is genuinely useful. However, it gives no guidance on when to delete versus adjacent alternatives such as mark_handled or update_item, so the choice of tool is only implied.

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