Skip to main content
Glama
CROW: LLM Wiki

CROW: LLM Wiki

Official

move_note

Move a note to another folder while preserving links to and from it; use when a user asks to relocate a single note without changing its text.

Instructions

Move one note into another folder; the links to and from it follow.

Call it when the user asks to move a note; to move every note of a top-level folder, use merge_areas. The note's text does not change and no model is called. Returns the note's new path; an unknown note returns an error.

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": {
      "path": "<path>",
      "folder": "<folder>"
    },
    "name": "move_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesThe note's path, e.g. finance/pricing.md
folderYesThe folder to file it in, e.g. /sourcing ("/" is the top level)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.4

TDQS

A4.5/5.0
Behavior4/5

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

Beyond the annotations (readOnly=false, destructive=false, openWorld=false), the description discloses meaningful behavior: inbound and outbound links follow the note, the note's text is untouched, no model is invoked, and an unknown note errors out. The link-propagation detail is the key side effect an agent would not otherwise know. It stops short of saying whether the move is reversible or what happens if the target folder does not exist, which keeps it off a 5.

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?

Three short sentences, each doing distinct work: what the tool does, when to call it and what to call instead, and what the caller can expect back. The scoping constraint is front-loaded and there is no 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?

For a two-parameter mutation tool with full annotation coverage and an output schema, the description supplies exactly the missing pieces: the link side effect, the guarantee that content is unchanged, no model cost, and the error case. Return-value details are already covered by the output schema, so nothing material 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 description coverage is 100% and both parameters carry examples and format notes in the schema, so the description is not required to explain them. It adds only indirect meaning — that an unknown `path` produces an error — without clarifying folder-path semantics beyond the schema. Baseline 3 applies.

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 and resource ("Move one note into another folder") and immediately bounds scope to a single note, which is exactly what separates it from the folder-wide sibling it names. An agent can distinguish it from merge_areas, delete_note or rename_area without opening any schema.

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 triggering condition ("Call it when the user asks to move a note") and names an explicit alternative with the condition that selects it (moving every note of a top-level folder → `merge_areas`). This is a clean when-to-use / when-to-use-something-else pair.

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