basic-memory

Move note

bm_move

Move or rename a Basic Memory note or directory within its project by specifying a destination path; optionally require a matching checksum so only the read revision is moved.

Instructions

Move or rename a Basic Memory note (identifier) or a directory (path) within its project. destination is the new project-relative path; ending it with '/' moves into that folder under the current name ('archive/'). A note keeps its file extension ('.markdown' may become '.md'). Pass expected_checksum (from bm_read) to move a note only if it is still the revision you read. Moving into another project is refused: bm_read, bm_write there, then bm_delete.

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": {
      "destination": "<destination>",
      "project": "<project>"
    },
    "name": "bm_move"
  }
}

Input Schema

Name	Required	Description	Default
`path`	No	The directory to move, with everything in it, e.g. 'drafts/2025'.
`project`	Yes	Required project name, 'workspace/project', or project external id. Discover projects with bm_project(command='list'). Paths are relative to this project; a qualified path must agree with it.
`identifier`	No	The note to move: a path, permalink, memory:// URL or exact title.
`destination`	Yes	New path, e.g. 'archive/plan.md'. A trailing '/' ('archive/') moves the note or directory into that folder under its current name.
`output_format`	No		text
`expected_checksum`	No	Move the note only while it is still this revision (from bm_read).

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedOct 31, 2026

removedInput schema / properties / project / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

removedInput schema / properties / project / default
```
Removed value: -null
```

changedInput schema / properties / project / description

Previous value: -"Project name, 'workspace/project', or project external id. Omit to use the default project."New value: +"Required project name, 'workspace/project', or project external id. Discover projects with bm_project(command='list'). Paths are relative to this project; a qualified path must agree with it."

addedInput schema / properties / project / minLength
```
Added value: +1
```
addedInput schema / properties / project / type
```
Added value: +"string"
```

changedInput schema / required

Previous value: -[
-  "destination"
-]New value: +[
+  "destination",
+  "project"
+]

changedOutput schema / properties / result / anyOf

Previous value: -[
-  {
-    "additionalProperties": true,
-    "type": "object"
-  },
-  {
-    "type": "string"
-  }
-]New value: +[
+  {
+    "type": "string"
+  },
+  {
+    "additionalProperties": true,
+    "type": "object"
+  }
+]

Addedv0.24.1Oct 23, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Goes well beyond the annotations (which only mark it as non-read-only, non-idempotent, non-destructive): it discloses the cross-project refusal, extension normalization ('.markdown' may become '.md'), preservation of the current name when destination ends in '/', and optimistic-concurrency behavior via expected_checksum. It does not say what happens if the destination path already exists, which is the one meaningful behavioral gap for a move operation.

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?

Four dense sentences with the core action and destination semantics front-loaded; the cross-project refusal and checksum note follow logically. Slightly packed with parenthetical detail, but no sentence is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists so return values need no explanation, and annotations cover the safety profile; the description fills in the refusal rule and checksum semantics. The missing piece is overwrite/collision behavior when the destination already exists, which matters for a move tool.

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 already 83%, so the baseline is 3; the description still adds meaning by framing `destination` as a project-relative path, explaining the trailing-'/' convention in operational terms, and tying `expected_checksum` to a prior bm_read. The extension-change note for notes is additional context not in 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+resource pair ('Move or rename a Basic Memory note or directory') and immediately disambiguates the two modes via the `identifier` vs `path` parameters. The within-project scope constraint further narrows what the tool does, letting an agent separate it from bm_edit (content change) and bm_delete.

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?

Gives an explicit when-not with the replacement workflow: cross-project moves are refused, so use bm_read, bm_write there, then bm_delete. It also specifies the conditional-move case via `expected_checksum` and the trailing-slash convention for moving into a folder without renaming.

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

Deploy Server