Skip to main content
Glama

move_note

Move a note to a specified folder using its note ID and target folder. Use the new note ID returned in the result, as the ID can change after moving.

Instructions

Move a note to a folder. The note id can change after a move. Use the id in the result.

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

Input Schema

NameRequiredDescriptionDefault
idYesNote id from search_notes (it starts with x-coredata://).
folderYesTarget folder name (any case) or id.
accountNoAccount name, for example iCloud. Ignores case.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, non-open-world mutation, so the safety bar is partly met structurally. The description then adds genuinely non-obvious behavior: the note id can change after a move and the caller must use the id returned in the result. That is exactly the kind of post-condition an agent would otherwise get wrong.

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, zero filler, with the action front-loaded and the critical id-changes caveat immediately after it. Every sentence carries information the agent needs.

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?

For a three-parameter, no-output-schema move operation, the definition covers the action, the id instability, and the correct follow-up source of truth. What remains unsaid is peripheral: error behavior when the folder does not exist, or whether a conflicting note name is renamed.

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%, so the id, folder, and account parameters are already documented in structured form, including the x-coredata:// prefix, case-insensitive folder names, and the iCloud example. The description's only parameter-adjacent note is about the result id, not the inputs, so it adds nothing beyond the schema baseline.

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?

States a specific verb and resource: 'Move a note to a folder.' An agent can immediately tell this is a relocation operation on notes rather than message movement or note content editing. It stops short of naming how it differs from similarly named siblings such as move_message, but the resource distinction is inherent.

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?

The description makes the operation obvious but gives no explicit when-to-use/when-not-to guidance, no mention of alternatives for relocating notes, and no stated prerequisites. Usage is implied by the verb and target rather than spelled out.

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