Skip to main content
Glama
Sign In

TransformPipe

by io.github.raudarlabs
OverviewDiscussionsAdmin

Convert HTML, CSV, JSON, text, RTF or Evernote to Markdown

tp_convert_to_markdown
Read-onlyIdempotent

Converts HTML, CSV, TSV, JSON, plain text, rich text (.rtf) or an Evernote export (.enex) to Markdown and returns it. Use it when the user provides one of these formats as text and wants Markdown. from names the source format. Nothing is saved to the account, and the output is limited to 40,000 characters; to save the result, call tp_save_document with the same source and from. Binary files (.docx, .xlsx, .pptx, .epub, .odt, export .zip) cannot be passed as tool arguments; they are converted in the TransformPipe app or with POST /api/v1/documents.

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": {
      "source": "<source>",
      "from": "<from>"
    },
    "name": "tp_convert_to_markdown"
  }
}

Input Schema

NameRequiredDescriptionDefault
fromYesThe source format.
nameNoA name for the result. JSON uses it as the document heading; the other formats ignore it.
sourceYesThe file content, as text.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent and non-destructive semantics, and the description adds real behavior beyond them: nothing is written to the account, output is capped at 40,000 characters, and binary inputs cannot be passed as arguments. It stops short of saying whether exceeding the limit truncates or errors, which is the one operational detail an agent still has to guess.

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 sentences, front-loaded with capability, then when-to-use, then constraints, then exclusions — no sentence is filler and the ordering matches how an agent reads a definition.

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?

There is no output schema, so the description carries the return-value burden and does it: Markdown text, length-capped, not persisted. Combined with the format list, persistence note and binary exclusion, an agent has everything needed to call this correctly on the first try.

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 earns a bump by tying `source` and `from` together as the pair to replay into tp_save_document and by framing `source` as text content rather than a file. It says nothing about the optional `name` parameter, which the schema alone must carry.

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 (converts ... to Markdown) plus the full set of accepted source formats, and the inverse sibling tp_convert_from_markdown makes the direction unambiguous. An agent can select this over any other sibling without opening the 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?

Gives an explicit trigger ('when the user provides one of these formats as text and wants Markdown'), names the follow-on tool tp_save_document with the parameter mapping needed to persist output, and rules out binary formats with the alternative paths (TransformPipe app or POST /api/v1/documents).

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