Skip to main content
Glama

json-to-md

JSON to Markdown. Any JSON document in, URL-encoded as the json query parameter (up to 12,000 bytes), a clean Markdown rendering out: object keys as headed sections, uniform object arrays as tables, scalar arrays as bullet lists. Price: $0.02 per call, paid in USDC on Base mainnet over x402; an unpaid call answers HTTP 402 with the exact machine-readable payment terms.

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": {
      "json": "<json>"
    },
    "name": "json-to-md"
  }
}

Input Schema

NameRequiredDescriptionDefault
jsonYesThe JSON document to render, as text (up to 12,000 bytes).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so well: it discloses the 12,000-byte input ceiling, the URL-encoding convention for the query parameter, the $0.02 per-call price, the payment rail (USDC on Base mainnet via x402), and that an unpaid call returns HTTP 402 with machine-readable terms. That is exactly the kind of pre-call cost and failure-mode context an unannotated tool needs.

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, each doing distinct work: what it produces, how to pass input, and what it costs. The transformation description is front-loaded and no sentence is padding.

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 one-parameter conversion tool with no output schema, the description covers input format, size limit, encoding, pricing, and output structure, so nothing an agent needs in order to call it correctly or anticipate a 402 is missing. Minor unknowns such as behavior on malformed JSON are secondary for a pure renderer.

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 single parameter is already documented, but the description adds transport semantics the schema omits entirely: the document must be URL-encoded and passed as the json query parameter. It reinforces the 12,000-byte limit consistently with the schema.

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?

Names a specific transformation (JSON to Markdown) and then describes the exact output shape: keys become headed sections, uniform object arrays become tables, scalar arrays become bullet lists. That level of detail lets an agent distinguish it from siblings like csv-convert or style-lint 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: 'Any JSON document in ... Markdown rendering out' tells the agent what the tool is for, but there is no explicit when-to-use, when-not-to-use, or named alternative for overlapping tasks (e.g., csv-convert for tabular input). The byte cap is a hard constraint the agent must respect, which is useful, but routing guidance is absent.

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.

Resources