Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

Markdown to HTML: render Markdown text as HTML

markdown_to_html
Read-only

Convert Markdown (headings, paragraphs, bold, italic, strikethrough, links, images, inline and fenced code, lists and task lists, tables, quotes, rules) to HTML. Raw HTML in the input is escaped, so the output is safe to embed. Use to publish agent-written Markdown on a web page. Example: markdown=# Title Some bold text and a link.. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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": "markdown_to_html"
  }
}

Input Schema

NameRequiredDescriptionDefault
markdownYesThe Markdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, non-destructive, closed-world), and the description adds genuinely new context: raw HTML in input is escaped so output is embed-safe, plus billing behavior (charged per call, first 25 free, failed calls free, non-idempotent in cost terms). It does not mention output structure or size/rate limits, but for a stateless converter the disclosure is solid.

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?

Capability and safety statement are front-loaded, followed by usage and pricing. The pricing/payment sentence is long and mixes two unrelated concerns, but it is materially useful cost information rather than filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter, stateless converter with no output schema, the description covers what is needed: input format coverage, escaping behavior, and cost. A brief note on the returned HTML (e.g. fragment vs document) would close the last gap.

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% for the single `markdown` parameter, so the schema already carries the semantics; the description only adds a worked example. This is the baseline case where the description neither compensates nor needs to.

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 concrete verb and resource ('Convert Markdown ... to HTML') and enumerates the supported Markdown constructs, which lets an agent check capability fit before calling. The reverse-direction sibling html_to_text is implicitly distinguished by the explicit source→target direction.

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 one concrete usage context — 'Use to publish agent-written Markdown on a web page' — with an inline example. It does not name an alternative or state when not to use it, so it stops short of full routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.