Skip to main content
Glama

convert_to_asciidoc

Idempotent

Convert Markdown to AsciiDoc format, transforming headers, code blocks, links, and images to AsciiDoc syntax. Supports GitHub-Flavored Markdown tables and KaTeX math expressions.

Instructions

Convert Markdown to AsciiDoc format. Transforms headers to = syntax, code blocks to ---- delimited blocks, links to url[text] syntax, and images to image::url[alt] directives.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
markdownYesThe raw Markdown source text to convert. Supports GitHub-Flavored Markdown (tables, task lists, strikethrough) and KaTeX math expressions. Pass the full document content as a string, not a file path.
output_pathNoOptional. Absolute or relative file path (e.g. './output.txt') where the result will be saved. Parent directories are created automatically. If omitted, the converted text content is returned directly in the response as a string. If provided, the file is written to disk and a JSON summary with { success, file_path, file_size_bytes, format } is returned instead.
Behavior4/5

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

Annotations cover idempotency and safety (readOnlyHint=false, destructiveHint=false). The description adds valuable transformation semantics: specific mappings for headers, code blocks, links, and images. It does not explicitly mention file I/O behavior, though output_path schema covers this.

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?

Two sentences total. First establishes purpose; second provides concrete syntax examples. Zero filler content. Every word earns its place by conveying AsciiDoc-specific formatting rules.

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?

Given the tool's straightforward conversion purpose, rich annotations, and comprehensive schema, the description is complete. It explains the transformation semantics adequately without needing to elaborate on return values (handled by schema).

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 coverage is 100% with detailed parameter descriptions (markdown supports GFM/KaTeX, output_path creates parent directories). Description focuses on transformation logic rather than repeating parameter specs, which is appropriate given the rich schema 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?

Description opens with specific verb 'Convert' and target format 'AsciiDoc', immediately clarifying scope. The detailed syntax transformations (= headers, ---- code blocks) distinguish it from siblings like convert_to_html or convert_to_rst that would produce different markup.

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?

No explicit 'when to use' or comparison with alternatives is stated. However, the specific AsciiDoc syntax examples (image::url, url[text]) implicitly signal this tool's domain versus other conversion siblings, providing contextual hints for selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/XJTLUmedia/MCP_Markdown_Formatter'

If you have feedback or need assistance with the MCP directory API, please join our Discord server