Skip to main content
Glama
Sign In

TransformPipe

by io.github.raudarlabs
OverviewDiscussionsAdmin

Delete a document

tp_delete_document
DestructiveIdempotent

Moves one document to the Trash of the user's TransformPipe account, where it is kept for 14 days and then deleted for good. Use it when the user asks to delete or remove a specific document. A shared link to the document stops working at once; tp_restore_document puts the document back, link and all, within the 14 days. confirm: true is required and is set after the user has named the document and agreed to delete it; without it nothing is deleted and the response shows which document would be deleted. To delete a folder together with its documents, call tp_delete_folder with with_documents: true.

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": {
      "id": "<id>",
      "confirm": "<confirm>"
    },
    "name": "tp_delete_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesDocument id from tp_list_documents.
confirmYesSet true after the user has asked for this document to be deleted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

It goes well beyond the annotations by disclosing the 14-day Trash retention, the fact that a shared link stops working immediately, the restore path via tp_restore_document, and the consequence of omitting `confirm` (a dry-run response that shows which document would be deleted). These details cover destructive scope, reversibility, and the confirmation gate, all of which the annotations only flag as 'destructive'.

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?

The effect is front-loaded and every sentence carries real information: the retention window, the restore path, the confirmation gate, and the folder alternative. The only cost is density, with four information-packed clauses that an agent must parse carefully, but no filler.

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 two-parameter destructive tool with 100% schema coverage and no output schema, the description covers effect, reversibility, timing, safety gate, and the sibling alternative. Nothing an agent needs in order to call it safely is missing.

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; the description adds meaning by framing `confirm` as the step that triggers the dry-run versus the delete. The `id` parameter gains nothing beyond the schema, which already points to tp_list_documents, so the gain is modest.

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 scope: it moves ONE document to the Trash of the user's account, and it distinguishes that action from tp_delete_folder with `with_documents: true`. An agent can separate this from tp_restore_document and from the folder-deletion sibling without opening either schema.

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?

It names the triggering condition ('when the user asks to delete or remove a specific document') and an explicit alternative for the folder case. It also states the precondition gating invocation, namely that `confirm: true` is set only after the user has named the document and agreed to delete it.

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