Skip to main content
Glama
Sign In

TransformPipe

by io.github.raudarlabs
OverviewDiscussionsAdmin

List documents

tp_list_documents
Read-onlyIdempotent

Lists the documents on the user's TransformPipe account, newest first, with each document's id, name, size, date, folder and sharing state. Use it when the user asks what documents they have or is looking for a document, or when another tool needs a document id. query matches document names and content; folder limits the list to one folder and its subfolders.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tp_list_documents"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of documents to return, newest first. Default 50.
queryNoText to match against document names and content.
folderNoA folder id from tp_list_folders, or a path from the top such as "Devart AI/Home". Lists that folder and its subfolders.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description still adds useful behavior: results are newest-first and each row carries id/name/size/date/folder/sharing state, and `query` searches both names and content while `folder` recurses into subfolders. It doesn't discuss pagination/truncation behavior at the 200 cap, which keeps it from a 5.

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?

Three sentences, front-loaded with what is returned and in what order, then when to use it, then parameter nuance. No redundant or filler wording.

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 no output schema, the description compensates by enumerating the returned fields, and with only three optional parameters it covers the filtering model adequately. An agent has everything needed to call it and interpret the result.

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 every parameter is already documented with constraints (limit 1-200, default 50) and format examples ("Devart AI/Home"). The description restates the query and folder semantics rather than adding new detail, so the baseline 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 (lists documents on the user's account) plus ordering (newest first) and the exact fields returned (id, name, size, date, folder, sharing state). This clearly separates it from tp_get_document (single doc), tp_search_documentation (product docs) and tp_list_folders.

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?

Gives concrete triggers: user asks what documents they have, is hunting for a document, or another tool needs a document id. It also explains how `query` and `folder` narrow the list. It stops short of naming alternatives for overlapping cases (e.g. when to prefer tp_get_document once an id is known), so not a full 5.

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