Skip to main content
Glama
Sign In
mcp-apple-notes

mcp-apple-notes

by Dan8Oren
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

move-note

Move a note to a different folder by providing its title or Apple Notes ID. Optionally specify the current folder to resolve duplicate titles.

Instructions

Move a note to a different folder. Identify note by noteId or title. Use list-folders to get available paths.

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": {
      "targetPath": "<targetPath>"
    },
    "name": "move-note"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoOptional current folder path to disambiguate duplicate titles
titleNoTitle of the note to move
noteIdNoApple Notes ID. If provided, skips title resolution.
targetPathYesFull folder path to move the note to (e.g. iCloud/Work/Projects)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are provided, so the description bears the full burden. It implies mutation (moving a note) and describes identification methods, but lacks details on side effects, error conditions, or behavior for ambiguous titles.

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?

Two sentences: first states core purpose, second covers identification and a helpful hint. No wasted words, front-loaded.

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?

Given 4 parameters and no output schema, the description covers identification and references list-folders for paths. It could mention what happens if targetPath doesn't exist, but overall adequate for a move operation.

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%, baseline 3. The description adds value by explaining the relationship between noteId and title as alternative identifiers, and notes the path parameter's role in disambiguation.

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 clearly states the verb 'move' and the resource 'note' with destination 'folder', distinguishing it from sibling tools like create-note, delete-note, etc.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains how to identify the note (by noteId or title) and suggests using list-folders to get available paths, providing clear context for usage. However, it doesn't explicitly state when not to use this tool or alternatives.

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

Deploy Server

Other Tools