NoteDiscovery MCP Server

move_note

Move or rename a note to a new path or folder, then identify notes with broken links so you can fix references.

Instructions

Move or rename a note to a different path. Use this to reorganize notes or rename them. Other notes do not change: the result lists the notes whose links to it no longer work.

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": {
      "old_path": "<old_path>",
      "new_path": "<new_path>"
    },
    "name": "move_note"
  }
}

Input Schema

Name	Required	Description	Default
`new_path`	Yes	New path for the note (can be in a different folder)
`old_path`	Yes	Current path of the note

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 24, 2026

TDQS

B3.4/5.0

Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose a genuinely useful side effect that the schema cannot convey: links in other notes break and the result enumerates them. It does not say what happens if new_path already exists, whether moves are reversible, or what permissions are needed, so material behavior for a mutation remains undisclosed.

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?

Three short sentences, front-loaded with the core action before usage and side effects. The final clause about broken links is dense but earns its place; wording is efficient with no filler.

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?

There is no output schema, and the description correctly compensates by describing the return (the list of notes with broken links). However, for a mutation tool with zero annotation coverage and no output schema, it leaves out destination-collision behavior and failure modes, so it is adequate but not complete.

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%, with both old_path and new_path documented in the input schema, so the baseline is 3. The description adds nothing parameter-specific beyond restating the "/different path" idea already present in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: "Move or rename a note to a different path." That is far clearer than the bare name and enough to distinguish it from siblings like get_note or delete_note, though it does not explicitly address overlap with edit_note or move_folder.

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?

It offers implied usage context ("Use this to reorganize notes or rename them"), which tells an agent the intent behind the tool. There is no explicit when-not guidance, no named alternative for content changes versus path changes, and no stated prerequisites, so the routing guidance stays at the implied level.

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