Skip to main content
Glama

Import a memory share link

import_memory_share
Idempotent

Use this when the user pastes a MemoryRouter share link (app.memoryrouter.ai/transfer/...) with its password and asks to import it. The first call (no confirmation) only shows who shared it and how many memories it holds, and imports nothing. After the user confirms, call again with the same link and password and the exact confirmation phrase to copy the memories into the connected vault. Importing is free. For a large share, call again with the same arguments until it reports complete.

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": {
      "link": "<link>",
      "password": "<password>"
    },
    "name": "import_memory_share"
  }
}

Input Schema

NameRequiredDescriptionDefault
linkYesThe share link, or just its token.
passwordYesThe share password, like MR-XXXX-XXXX-XXXX-XXXX.
confirmationNoExact phrase, only after the user has seen the summary and confirmed.

Output Schema

NameRequiredDescriptionDefault
labelNo
totalNo
copiedNo
failedNo
statusNo
previewNo
skippedNo
importedYes
processedNo
shared_byNo
duplicatesNo
memory_countNo
estimated_tokensNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already flag a write (readOnlyHint=false, destructiveHint=false, idempotentHint=true), and the description adds real context beyond them: the first call is effectively a read-only preview that imports nothing, the second call performs the copy, importing is free, and repeat calls are needed for large shares. This is consistent with, not contradictory to, the idempotent/non-destructive profile.

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?

Four sentences, all load-bearing, with the trigger clause front-loaded and the two-phase behavior following immediately. The 'Importing is free' note is short and informative rather than filler.

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 an output schema exists, the description need not explain return values, and it still covers the preview-vs-commit distinction, the confirmation gate, cost, and multi-call resumption. Nothing an agent needs in order to drive this three-parameter, two-step tool is missing.

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 workflow meaning the schema cannot: the confirmation phrase is only for the post-summary call, and the link/password must be resupplied identically on subsequent calls. It doesn't explain that the link may be passed as a bare token, which the schema does cover.

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 title and description state a specific verb and resource ('Import a memory share link') and immediately clarify the two-phase shape: a preview call that 'imports nothing' followed by a confirmed copy 'into the connected vault'. That is clearly distinct from siblings like create_memory_share or revoke_memory_share, which operate on the sharing side.

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?

The trigger is explicit: 'Use this when the user pastes a MemoryRouter share link ... with its password and asks to import it.' It also gives the sequencing rule (call first without confirmation, then with it) and the loop rule for large shares, so the agent knows exactly when to call and when not to proceed.

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.

Resources