Skip to main content
Glama
Life Admin MCP

Life Admin MCP

by NKC27

Restore item

restore_item

Restore a recently deleted item by its title to recover accidental deletions from your local life admin records.

Instructions

Bring back the most recently deleted item with this title.

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": "restore_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemYesThe deleted item's title

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

Annotations declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false, and the description does add one genuinely useful behavioral detail beyond them: only the MOST RECENTLY deleted item with that title is recovered, which explains the non-idempotent flag. However, it says nothing about what happens when no matching deleted item exists, whether the restored item returns to its original location, or whether the operation can fail silently — significant gaps for a mutation 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?

A single sentence with zero padding, and the most decision-relevant qualifier ('most recently deleted') is placed before the identifier. Nothing is wasted or buried.

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?

For a one-parameter tool with annotations present and no output schema, the definition covers the core action, but it omits failure behavior and post-restore state, which matter for a non-idempotent mutation. It is workable but not complete enough to call confidently without trial.

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 schema already documents the single parameter as 'The deleted item's title'. The description's only added meaning is that the title resolves to the most recent deletion, which refines how the value is interpreted but is already largely conveyed by the phrase 'most recently deleted' under purpose clarity. Baseline 3 is appropriate.

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?

Names a specific verb (bring back / restore) and a specific resource (the most recently deleted item), with the title-based lookup made explicit, which cleanly separates it from delete_item, add_item, and get_item. It stops short of naming a sibling or stating scope limits, so it is clear but not maximally differentiated.

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?

Usage is only implied: an agent can infer this is for undoing a deletion, but there is no explicit 'use this when...' clause, no alternative named, and no note about what to do if the item was never deleted or already restored. The definition leaves selection entirely to inference.

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