Skip to main content
Glama

convert_to_latex

Idempotent

Convert Markdown to LaTeX source code for research papers and PDF compilation. Transforms sections, formatting, lists, tables, and math expressions into valid .tex syntax. Export to file or return as string for pdflatex or xelatex workflows.

Instructions

Convert Markdown to LaTeX source code. Produces a LaTeX document fragment with \section, \textbf, \textit, \begin{itemize}/\begin{enumerate} list environments, verbatim code blocks, and table environments. KaTeX math expressions in the Markdown are passed through as native LaTeX math. Side effects: when output_path is provided, writes the .tex file to disk (creates parent directories, overwrites existing files). When output_path is omitted, returns the LaTeX source as a string. Returns: LaTeX source string (if no output_path), or JSON { success, file_path, file_size_bytes, format } (if output_path set). Use this when you need to embed content in a LaTeX workflow or compile to PDF via pdflatex/xelatex externally. For direct PDF output without a LaTeX toolchain, use convert_to_pdf instead.

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 indicate idempotentHint=true and readOnlyHint=false, but the description adds critical behavioral context: it discloses file system side effects ('writes the .tex file to disk'), directory creation behavior ('creates parent directories'), and overwrite behavior ('overwrites existing files'). It also explains the dual return mode (string vs JSON object) which annotations do not cover.

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?

Six sentences covering purpose, output format specifics, side effects, return values, and usage guidelines. Every sentence provides distinct information not replicated elsewhere. Slightly dense but necessary given the tool's conditional behavior (file write vs. string return).

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?

Comprehensive coverage for a conversion tool: input format details (GFM, KaTeX), output structure (specific LaTeX environments like itemize, verbatim), side effects (file I/O), return value schemas for both branches, and sibling alternatives. No output schema exists, and the description adequately compensates by documenting both possible return structures.

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?

While schema coverage is 100% (baseline 3), the description adds significant behavioral meaning to output_path by explaining that its presence triggers file write side effects and changes the return type from string to JSON object. This contextualizes the parameter beyond the schema's functional definition.

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 opens with a specific verb and resource ('Convert Markdown to LaTeX source code') and immediately distinguishes from the sibling tool convert_to_pdf by stating 'For direct PDF output... use convert_to_pdf instead.' It clearly scopes the conversion domain (Markdown→LaTeX) amidst a large family of conversion tools.

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

Usage Guidelines5/5

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

Explicitly states when to use ('when you need to embed content in a LaTeX workflow or compile to PDF via pdflatex/xelatex externally') and provides a clear alternative for the opposite case ('For direct PDF output without a LaTeX toolchain, use convert_to_pdf instead'). This directly addresses sibling 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