Skip to main content
Glama
Sign In

TransformPipe

by io.github.raudarlabs
OverviewDiscussionsAdmin

Rename or move a folder

tp_update_folder
Idempotent

Renames a folder, moves it under another folder or to the top level, or both; its documents and subfolders move with it. Use it when the user asks to rename, move or reorganise a folder. parent is an existing folder's id or path, or null or "" for the top level. A folder cannot be moved into itself or into one of its subfolders. When the destination is shared, or inside a shared folder, its readers gain access to this folder's contents, so confirm: true is required; without it nothing changes and the response says who would gain access. Renaming 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": {
      "folder": "<folder>"
    },
    "name": "tp_update_folder"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoIts new name. Omit to keep the current one.
folderYesThe folder to change: an id from tp_list_folders, or a path from the top.
parentNoDestination: an existing folder's id or path from the top, or null or "" for the top level. Omit to keep it where it is.
confirmNoRequired when the destination is shared or inside a shared folder. Set true after the user has agreed that its readers can read this folder's contents.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only declare idempotent/non-destructive semantics, while the description discloses substantive behavior: children move with the folder, self/subfolder moves are forbidden, shared destinations grant readers access, and without confirm nothing changes and the response reports who would gain access. Renaming is explicitly stated to need no confirmation.

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?

Front-loaded with the action, then the usage trigger, then the parameter and confirmation rules in order of need. Every sentence carries distinct information with no padding.

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 the essential preconditions (shared destination confirmation), the failure mode, and the side effect on contents. Nothing an agent needs to invoke it safely is missing.

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 coverage is 100%, so parameter meanings are already documented. The description mostly restates `parent` and `confirm` rather than extending them, adding only the self/subfolder constraint and the no-op consequence of omitting confirm.

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 plus scope: 'Renames a folder, moves it under another folder or to the top level, or both; its documents and subfolders move with it.' This clearly separates it from siblings like tp_move_documents (documents) and tp_create_folder (creation).

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?

'Use it when the user asks to rename, move or reorganise a folder' gives a clear trigger, and the confirm rule explains exactly when confirmation is and isn't needed. It stops short of naming sibling alternatives (e.g. moving documents instead), so alternatives are left implicit.

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

All TransformPipe 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