phygital-memory

Official

Overview Schema Source Related Servers Discussions Admin

move_note

Move or rename a note, file, or subfolder within the same memory; it refuses an existing target path to prevent overwrites and returns old and new paths.

Instructions

Move or rename a note, file or subfolder to a new path within the same memory (not into another memory). A subfolder moves with everything in it; its version history and AI tasks follow, and a private folder stays private. Refuses if something already exists at new_path, so nothing is overwritten. Links to it in other notes are not rewritten: check them with links_to. Use trash_note to remove something instead. Needs Allow edits. Returns the old and new path.

Input Schema

Name	Required	Description
`path`	Yes	The note's or file's path in the folder, like 'Projects/plan.md' (from list_notes or a search result).
`folder`	No	Which unlocked folder (its name, from status). Leave empty when only one is open.
`private`	No	True only when the person asked, in this chat, for something in a folder they keep private.
`new_path`	Yes	Where it goes, like 'Archive/plan.md'. Also renames.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 29, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond annotations it discloses key behavior: refuses to overwrite an existing new_path, subfolder contents and version history/AI tasks move along, private folders stay private, and inbound links are NOT rewritten. It also states the return value (old and new path) and the auth requirement. This is exactly the extra context annotations alone cannot convey.

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?

Dense but front-loaded: the primary action and scope come first, followed by side effects and alternatives. Every sentence carries a distinct constraint or behavior; nothing is wasted.

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 an output schema present, return values needn't be detailed, yet it still notes the old/new path. Annotations cover the safety profile, and the description fully covers permissions, overwrite refusal, side effects, and link caveats – nothing material 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 real meaning: new_path also renames, must not already exist, and the move must stay within the same memory. It doesn't document folder/private params, but the schema handles those.

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 opens with a specific verb pair and resource ('Move or rename a note, file or subfolder') and immediately bounds scope ('within the same memory, not into another memory'). It is trivially distinguishable from siblings like trash_note and links_to, which it names explicitly.

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?

It states the negative case (not into another memory, so use a different memory workflow), routes removal to 'trash_note', and points link-checking to 'links_to'. It also names the prerequisite ('Needs Allow edits'), covering when/when-not/alternatives.

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

Deploy Server