OnlyMCP

Move a memory file

memory_move

Move or rename one memory file; one file per call, a folder is not moved as a whole. Meant for reorganising without breaking links: by default every [[link]] that would no longer find the file is rewritten in the files that hold one, whatever its form (a name, a path, an alias, a heading), and the file keeps its history, which a new copy would not. A file you may only read is left alone. Answers "Moved to " with how many files had links rewritten and how many were left alone. Set updateLinks to false only when old links should stay as written.

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": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "memory_move"
  }
}

Input Schema

Name	Required	Description
`to`	Yes	New path.
`from`	Yes	Current path.
`updateLinks`	No	false to leave links alone. Default true.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations only declare the mutation/safety profile (readOnlyHint=false, destructiveHint=false). The description adds real behavioral context beyond them: default rewriting of every [[link]] form (name, path, alias, heading), history preservation that a copy would lose, silent skipping of read-only files, and the exact response text with link counts.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The scope constraint and the default link-rewriting behavior are front-loaded, and the response format comes last. Sentences are long and clausal but each carries distinct information; nothing is 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?

With no output schema, the description still reports the return value verbatim and its counts, and it covers the side effects, failure-adjacent case (read-only file) and parameter default. Nothing needed to call it correctly is missing.

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 from and to are already documented. The description clarifies what updateLinks controls (link rewriting across files that hold a link) rather than just its false/true meaning, which adds modest value over the schema.

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 ('Move or rename one memory file') and immediately scopes it ('one file per call, a folder is not moved as a whole'), which separates it from memory_write, memory_delete and list_memory.

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?

Gives clear operating conditions: one file per call, folders are not moved, read-only files are skipped, and updateLinks=false is reserved for the case where old links should stay as written. It does not name a sibling alternative for copying versus moving, but the when-to-use context is explicit.

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

All OnlyMCP tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?