Mathfold

convert_markdown

Render Markdown (LaTeX/AsciiMath formulas in any delimiter style, Mermaid diagrams, GFM tables, code) into a Word .docx with native equations or a PDF. Wide tables and diagrams are laid out automatically. Returns a temporary download link.

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": "convert_markdown"
  }
}

Input Schema

Name	Required	Default
`toc`	No
`theme`	No	standard
`title`	No
`format`	No	docx
`markdown`	Yes
`pageSize`	No	A4

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 28, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that wide tables and diagrams are laid out automatically and that the result is a temporary download link, but it does not state link expiry, permission requirements, size limits, or failure behavior.

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 three tight sentences with no wasted wording. The core conversion action and supported inputs are front-loaded, followed by layout behavior and return format.

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 tool with no annotations, no output schema, and zero parameter descriptions, the description covers the main purpose, some capabilities, and the return shape. However, it leaves significant gaps around parameter usage and operational constraints such as temporary-link lifetime.

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

Parameters2/5

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

Schema description coverage is 0% across six parameters, and the description only indirectly maps to the format option by mentioning .docx and PDF. It adds no meaning for toc, theme, title, pageSize, or the required markdown field, leaving most parameters undocumented.

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 states a specific verb and resource: render Markdown into a Word .docx or PDF. It also names distinguishing capabilities such as native equations, Mermaid diagrams, and automatic wide-table layout, so an agent can immediately tell what the tool does.

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 by the conversion task, but there is no explicit guidance on when to choose this tool, when not to use it, or any prerequisites. With no siblings, some context is naturally supplied, but the description does not actively route usage decisions.

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

All Mathfold tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?