Skip to main content
Glama
Sign In
Vestige

Vestige

by samvallad33
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

restore

Restore memories from a JSON backup file, supporting MCP wrapper, RecallResult, or direct memory array formats. Use the merge option to combine with existing data.

Instructions

Restore memories from a JSON backup file. Supports MCP wrapper format, RecallResult format, and direct memory array format.

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

Input Schema

NameRequiredDescriptionDefault
pathYesPath to the backup JSON file to restore from
mergeNoFor portable archives, merge into the current database instead of requiring an empty target. Applies sync tombstones and keeps newer local memory rows on conflict.
allowAnyPathNoAllow restoring from a file outside the active Vestige backups/ or exports/ directories. Only set true for trusted local files.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.6.0
  2. Removedv2.3.0
  3. First observedv2.1.27

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It omits that this is likely a destructive write operation, whether it overwrites existing memories, or any safety/reversibility caveats. The only extra behavioral detail is the supported file formats.

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 concise sentences, with the core purpose front-loaded and the format details placed right after. Every sentence earns its place.

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?

The schema provides rich descriptions for all parameters and the description covers formats, but the tool is not complete for safe invocation without knowing the destructiveness of a restore and what happens to existing memories. No output schema or annotations exist to fill that 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 description coverage is 100%, and each parameter already has a clear description. The tool description adds no parameter-level meaning beyond what the schema provides, so the 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?

The description states a specific action ('Restore memories') and target ('from a JSON backup file'), and the format enumeration adds precision. This clearly differentiates it from siblings like backup or export.

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?

The description implies the restoration use case but does not explicitly say when to choose this tool over alternatives like backup or export, nor does it state exclusions such as prerequisites like an empty target database. The schema's merge parameter hints at context, but the description itself lacks when/when-not guidance.

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