Skip to main content
Glama

Restore Memo

restore-memo
Idempotent

Restore a memo that was deleted (archived) with delete-memo, while it is still within the 45-day window before permanent erasure. Clears the archive flag so the memo is active, searchable and listed again. Find restorable memos with search-memo using archived: true. After 45 days the memo is erased for good and can no longer be restored.

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": {
      "id": "<id>"
    },
    "name": "restore-memo"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesId of the archived memo to restore (e.g. from search-memo with archived: true)
reasonNoOptional short line on why it is being restored, written to the change history and shown in the activity feed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false), and the description adds real behavioral context beyond them: the exact side effect ('clears the archive flag so the memo is active, searchable and listed again') and the hard 45-day expiry after which restoration is impossible.

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 core action, then the discovery path, then the failure boundary. No sentence is redundant.

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?

With no output schema, the description still covers everything an agent needs: what it does, the preconditions, the side effects, and the irreversible deadline. No gaps for a 2-parameter mutation tool.

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%, so both the id and reason parameters are already fully documented in the schema (including that reason is written to change history). The description only echoes the origin of the id via search-memo, adding little beyond the structured fields; baseline 3 is appropriate.

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?

States a specific verb and resource ('Restore a memo that was deleted') and immediately scopes it to the 45-day window. It is clearly distinguishable from sibling delete-memo, which it explicitly references as the inverse operation.

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

Usage Guidelines5/5

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

Gives the condition for use (still within the 45-day window), the condition under which it fails (after 45 days the memo is gone), and routes the agent to search-memo with archived: true to find candidates. Nothing about when to reach for this tool is left to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.