notlai-mcp

Overview Schema Source Related Servers Discussions Admin

notlai_move_note

Move a note into a specific folder or back to root to reclassify and organize your notes. Requires note ID and target folder ID from list_folders.

Instructions

Move a note into a folder, or back to root. Use this to reclassify and organize your notes. Use notlai_list_folders to find folder IDs.

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": {
      "noteId": "<noteId>",
      "folderId": "<folderId>"
    },
    "name": "notlai_move_note"
  }
}

Input Schema

Name	Required	Description	Default
`noteId`	Yes	The note ID to move (ULID format)
`folderId`	Yes	Target folder ID to move the note into, or null to move back to root (no folder)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.7.0Jul 28, 2026

TDQS

A4.2/5.0

Behavior3/5

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

No annotations exist, so the description must convey behavioral traits. It mentions moving into a folder or root but does not detail side effects (e.g., changes to note metadata, permissions, or undo behavior). The move operation is inherently non-destructive, but more disclosure would improve transparency.

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?

The description is two sentences, each serving a distinct purpose: stating the action and providing usage guidance. It is front-loaded with the core functionality and wastes no words.

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 2-parameter tool with no output schema and no annotations, the description covers the essential use case and gives a practical tip for parameter preparation. It could mention result details (e.g., whether the note object is returned) but is otherwise sufficient for an agent to invoke correctly.

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%, so baseline is 3. The description adds meaning by explaining the folderId's null option ('back to root') and directing to notlai_list_folders for IDs, which is valuable beyond the schema's type-only descriptions.

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 action: moving a note into a folder or back to root. It distinguishes the tool from siblings like notlai_create_note or notlai_delete_note by specifying the exact operation and target, including the null case for moving to root.

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?

It explicitly ties the tool to reclassification and organization, and advises using notlai_list_folders to find folder IDs. This provides clear context for when to use it, though it does not explicitly exclude alternative tools or set negative examples.

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