TransformPipe

Move documents to a folder

tp_move_documents

Idempotent

Moves documents into a folder, or out of all folders with folder: null. Use it when the user asks to file, move or organise documents in a folder, or to take them out of one. ids are document ids from tp_list_documents; folder is a folder id or path and must already exist. When the folder is shared, or inside a shared folder, its readers can read the moved documents, so confirm: true is required; without it nothing moves and the response says who would gain access. Moving documents out of a shared folder needs no confirmation.

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": {
      "ids": "<ids>",
      "folder": "<folder>"
    },
    "name": "tp_move_documents"
  }
}

Input Schema

Name	Required	Description
`ids`	Yes	Ids of the documents to move, from tp_list_documents.
`folder`	Yes	Destination folder: an id, or a path from the top. null or "" takes the documents out of all folders.
`confirm`	No	Required when the destination folder is shared or inside a shared folder. Set true after the user has agreed that its readers can read these documents.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 4, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the annotations, it discloses the confirmation gate, the exact failure behavior without `confirm` ('nothing moves and the response says who would gain access'), and the permission side effect that readers of a shared folder gain read access to the moved documents. The requirement that the folder must already exist is also stated, none of which is derivable from the annotations.

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 core action and the null case are front-loaded in the first sentence, followed by usage, parameter sourcing, and the confirmation rule. Every sentence carries distinct information with no restatement of the tool name or schema.

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?

With three parameters, no output schema, and no enums, the description covers everything an agent needs: when to call, what the parameters mean in context, the confirmation prerequisite, and what the response contains on refusal. Nothing material is left to inference.

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 the baseline is 3, but the description adds real meaning: `folder` must already exist, `confirm` is conditional on sharing rather than a blanket requirement, and `ids` is sourced from tp_list_documents. The schema already covers the id/path/null semantics, so this is additive rather than transformative.

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 states a specific verb and resource ('Moves documents into a folder') and covers both directions of the operation, including the `folder: null` removal case. It is clearly distinguishable from siblings such as tp_create_folder, tp_delete_document and tp_update_document.

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 gives explicit trigger conditions ('when the user asks to file, move or organise documents in a folder, or to take them out of one') plus a when-not style exception ('Moving documents out of a shared folder needs no confirmation'). What it lacks is a named alternative sibling to route to, so it falls short of the top band.

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

All TransformPipe tools Inspect

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.