agent-utils-mcp

tool_markdown_to_html

Convert Markdown text to HTML for rendering in web contexts.

Instructions

Convert Markdown 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": {
      "md_text": "<md_text>"
    },
    "name": "tool_markdown_to_html"
  }
}

Input Schema

Name	Required	Description	Default
`md_text`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 7, 2026

TDQS

C2.8/5.0

Behavior1/5

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

No annotations are provided and the description discloses no behavioral details. It does not mention side effects, error handling, invalid input behavior, or whether the conversion is pure and non-destructive.

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, front-loaded sentence with no redundant words or filler. It states the core transformation immediately and avoids unnecessary detail.

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

Completeness3/5

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

For a one-argument pure conversion tool, the description covers the essential purpose, but it leaves gaps in parameter explanation and edge-case behavior. It is probably sufficient for a simple call, yet it relies heavily on the parameter name and tool name to complete the context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema provides only the parameter name 'md_text' with no description coverage, and the tool description does not elaborate on expected values, format, or constraints. The only clue to the parameter's meaning comes from the tool name and purpose, not from explicit parameter documentation.

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 uses a specific verb ('Convert') and names both source and target formats ('Markdown to HTML'), making the tool's function unambiguous. It also clearly distinguishes the tool from its sibling tool_html_to_markdown, which performs the inverse operation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The description only restates the conversion function and does not explicitly say when to choose this tool over alternatives. There is no mention of use cases, constraints on input, or comparison with the sibling html-to-markdown tool.

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

Deploy Server