Skip to main content
Glama
Sign In

TransformPipe

by io.github.raudarlabs
OverviewDiscussionsAdmin

Convert Markdown to HTML, Confluence, Jira or Slack

tp_convert_from_markdown
Read-onlyIdempotent

Converts Markdown to sanitised HTML, Confluence storage format, Jira wiki markup or Slack mrkdwn and returns the result. Use it when the user wants Markdown as HTML, or as markup to paste into Confluence, Jira or Slack. The input is GitHub Flavored Markdown; raw HTML in it is sanitised. standalone: true returns a complete HTML document with inline styles. Nothing is saved to the account, and the output is limited to 40,000 characters. To keep the document on the account, call 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": {
      "markdown": "<markdown>"
    },
    "name": "tp_convert_from_markdown"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoOutput format: `html` (default), `confluence` (storage format, with code macros, info and warning panels and task lists), `jira` (wiki markup) or `slack` (mrkdwn, for a bot, a webhook or chat.postMessage).
nameNoTitle of a standalone document. Default "document".
themeNoColour palette of a standalone document. Default light.
markdownYesThe Markdown source.
standaloneNoWhen true, return a complete HTML document with inline styles; when false, an HTML body fragment. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations by disclosing that raw HTML is sanitised, that nothing is written to the account, that output is capped at 40,000 characters, and how standalone changes the returned document.

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 tight sentences, front-loaded with the core action and formats, then constraints, then the sibling alternative — no filler or repetition.

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 stateless conversion tool with no output schema, it covers input dialect (GFM), sanitisation, size limit, persistence semantics, and the save-document alternative — everything needed to call it correctly.

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%, including enum explanations for to and theme, so the schema already carries the parameter burden. The description only reinforces `standalone: true` (complete HTML document with inline styles) and adds nothing for name or theme.

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?

Opens with a specific verb+resource ("Converts Markdown") and enumerates all four target formats, so an agent can immediately tell it apart from sibling tp_convert_to_markdown or tp_save_document.

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?

Explicitly states when to use it ("when the user wants Markdown as HTML, or as markup to paste into Confluence, Jira or Slack") and names the alternative path for the opposite need ("To keep the document on the account, call tp_save_document").

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