Skip to main content
Glama
Sign In

ThreadPage

by page.thread
OverviewDiscussionsAdmin

Move a note to another thread

move_note
DestructiveIdempotent

Move a Note into another Thread. It stays the same Note: its id, time, history, pin, images and references go with it; move_thread moves a whole Thread. Refused for a Note with an unfinished request (request_open), in Trash (restore_note first) or in an archived Thread. Can edit and organize moves any Note; Can add notes only the Notes it added. expected_revision is not compared. Answers a receipt with the new revision and url.

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": {
      "operation_id": "<operation_id>",
      "note_id": "<note_id>",
      "expected_revision": "<expected_revision>",
      "thread_id": "<thread_id>"
    },
    "name": "move_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
note_idYesA Note's id, from get_thread, search or get_note.
thread_idYesThe Thread it goes to: a live, unarchived Thread within your access.
operation_idYesA new UUID for each write. After a lost answer, send the identical call with the same one, or check get_operation before writing again.
expected_revisionYesIts revision from list_threads, get_thread, list_folders or get_note (not a content_revision); not compared.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / expected_revision / description
      Previous value: -"The revision you last read for it."New value: +"Its revision from list_threads, get_thread, list_folders or get_note (not a content_revision); not compared."
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false; the description adds real value on top by listing the three refusal states, the permission scopes that gate success, and the receipt returned ('new revision and url'). The one slightly odd disclosure is that expected_revision is not compared despite being required, which is important but is also already stated in the schema.

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?

Front-loaded with the core action and the key sibling distinction, then refusal conditions, then permissions. Dense but nearly every clause carries information; the middle sentences ('Can edit and organize moves any Note; Can add notes only the Notes it added') are slightly compressed and read awkwardly but are not wasteful.

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 mutation tool with no output schema, the description covers preconditions, failure modes, permission scoping, idempotency/retry behavior, and the shape of the response. An agent has everything needed to decide whether to call it and how to recover from a refusal.

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 all four parameters are already documented in the schema, including the 'not compared' note on expected_revision and the operation_id retry guidance. The description restates the expected_revision caveat rather than adding new parameter meaning, so the baseline of 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?

States a specific verb and resource ('Move a Note into another Thread') and immediately delimits scope by contrasting with the sibling: 'move_thread moves a whole Thread.' It also enumerates what travels with the Note (id, time, history, pin, images, references), so an agent knows exactly what the operation preserves.

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?

Gives explicit when-not conditions: refused for a Note with an unfinished request, in Trash (with the alternative 'restore_note first'), or in an archived Thread. It also names the nearest alternative (move_thread) and states the permission split between 'Can edit and organize' and 'Can add notes', with get_operation implied via the operation_id guidance.

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

All ThreadPage toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources