TransformPipe

Create a folder

tp_create_folder

Idempotent

Creates a folder on the user's TransformPipe account, at the top level or inside parent, and returns its id and path. Use it when the user asks to create or add a folder. parent is an id or a path such as "Devart AI/Home"; missing folders on that path are created. If a folder with the same name already exists in that place, that folder is returned and nothing is created. To put documents into a folder, call tp_move_documents, or pass folder to tp_save_document.

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": {
      "name": "<name>"
    },
    "name": "tp_create_folder"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes	Name of the new folder. A path such as "Guides/2026" creates each missing folder on it.
`parent`	No	Parent folder: an id from tp_list_folders, or a path from the top. Omit for the top level.

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, the description discloses the upsert behavior (an existing same-name folder is returned and nothing is created), the side effect that missing folders on a `parent` path are created, and the return value (id and path). That goes well past what idempotentHint and destructiveHint convey on their own.

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?

Four short sentences, front-loaded with purpose, then the trigger, then parameter behavior, then the pointer to sibling tools. Every sentence carries information an agent would otherwise have to guess.

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 only two flat parameters, full schema coverage, and no output schema, the definition covers everything needed: when to call it, what the parameters accept, the idempotent side effect, and what is returned. Nothing material is left unstated.

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 meaning the schema does not: that `parent` accepts either an id or a slash-separated path, and that missing folders along that path are created as a side effect. The `name` path behavior is largely restated from the schema.

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 opens with a specific verb and resource ('Creates a folder on the user's TransformPipe account') and states the scope (top level or inside `parent`) plus the return value (id and path). It also names two sibling tools (tp_move_documents, tp_save_document) so the agent can distinguish filing actions from 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?

It gives an explicit trigger ('Use it when the user asks to create or add a folder') and routes document placement to tp_move_documents or tp_save_document's `folder` argument. It stops short of stating when NOT to use it, e.g. that renaming or moving an existing folder belongs to tp_update_folder, which sits among the siblings.

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.