Engram Obsidian Memory Sync

Restore Deleted

restore_deleted

Idempotent

Undo a delete_note, delete_folder or delete_attachment call: pass the delete_op_id it returned and everything that call removed comes back at its old path, while still in trash. An item whose path is now taken by another file, or whose trash window has passed, is skipped and listed. Safe to repeat: a second call restores nothing more. Refused if restoring would pass a plan limit.

Input Schema

Name	Required	Description	Default
`op_id`	Yes	The delete_op_id a delete tool returned
`vault_id`	No	Target vault: its name (e.g. "Engram") or its UUID. REQUIRED when you own more than one vault; the server keeps no active-vault state between calls, so it must be passed on every vault-scoped call. Omit only if you have a single vault. Call list_vaults if a name does not resolve.

Output Schema

Name	Required	Description
`notes`	Yes	Notes restored
`folders`	Yes	Empty folders restored
`skipped`	Yes	Items not restored and why: path_taken (another file holds the path), expired (past trash retention), unavailable (attachment bytes already reaped), changed (the item changed since the delete), unreadable
`attachments`	Yes	Attachments restored
`search_note`	No	When search will see this change; use get_notes until then
`search_indexing_starts_in_seconds`	No	At least this many seconds until indexing starts; search can lag further. Use get_notes to read the note until search finds it

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 1, 2026

addedOutput schema / properties / search_indexing_starts_in_seconds

Added value: +{
+  "description": "At least this many seconds until indexing starts; search can lag further. Use get_notes to read the note until search finds it",
+  "type": "integer"
+}

addedOutput schema / properties / search_note

Added value: +{
+  "description": "When search will see this change; use get_notes until then",
+  "type": "string"
+}

AddedOct 28, 2026

TDQS

A4.7/5.0

Behavior5/5

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

The description adds substantial behavioral detail beyond the annotations: restored items return to their old paths, remain in trash, skipped items are listed, repeats are safe, and plan limits can cause refusal. These details are consistent with the declared idempotent, non-destructive mutation behavior.

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 front-loaded with the core action and then proceeds through important edge cases in a compact sequence. Every sentence contributes operational meaning, with no wasted text.

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 the annotations, 100% parameter description coverage, and the presence of an output schema, the description gives an agent everything needed to decide when and how to call it. It covers the important failure and safety behaviors without needing to explain return values.

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 the baseline is 3, but the description adds useful meaning by clarifying that op_id refers to an entire delete call and restores everything that call removed. It does not add much for vault_id beyond the schema, but the op_id clarification is valuable.

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 states a specific verb and resource: undo delete_note, delete_folder, or delete_attachment by passing the returned delete_op_id. It clearly distinguishes the tool from its sibling delete operations and explains that all removed items are restored to their old paths while remaining in trash.

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?

It clearly says to use this after a supported delete call and to pass the delete_op_id that call returned. It also describes conditions where items are skipped or the operation is refused, though it does not explicitly compare against any alternative restore path.

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

All Engram Obsidian Memory Sync tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.