ZapifyAPI MCP Server

markdown_to_html

Convert Markdown text into clean HTML output. Provides a straightforward way to transform Markdown documents for web display.

Instructions

Convert Markdown text to HTML.

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

Name	Required	Description	Default
`markdown`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 3, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden. It states the primary action but does not disclose details like Markdown flavor support, output handling, potential errors, or side effects. For a simple conversion tool, this is adequate but not rich.

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?

The description is a single, clear sentence with no wasted words. It is front-loaded and directly conveys the tool's purpose.

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 simple single-parameter conversion tool, the description is largely complete. It lacks an output schema, but the return value is implied by the tool's purpose. No significant gaps are present for typical use.

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?

The schema has no descriptions for the parameter, so the description must compensate. It does mention 'Markdown text,' which aligns with the 'markdown' parameter, but adds no additional format or usage details beyond what the parameter name and type already imply.

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?

The description clearly states the tool's function: converting Markdown text to HTML, using a specific verb and resource. It is distinct from sibling tools like convert_currency or csv_to_json, which perform different conversions.

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?

The intended use is implied by the purpose, but no explicit guidance is given about when to use this tool versus alternatives, nor are any exclusions or prerequisites mentioned. It lacks clear context for selection among the many converter siblings.

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