Skip to main content
Glama
MathMagic MCP Pro

MathMagic MCP Pro

by mrtersn9-cpu

mathmagic_export_equation

Render LaTeX equations to a file and choose the output format via the file extension, including PDF, SVG, PNG, MathML, and LaTeX.

Instructions

Render LaTeX with MathMagic to a file; format from the extension: .eps .pdf .svg .png .jpg .gif .bmp .wmf .mmf .mml/.mathml/.html (MathML) .tex (LaTeX, ams=true for AMS) .amath .mathtxt.

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": {
      "latex": "<latex>",
      "out_path": "<out_path>"
    },
    "name": "mathmagic_export_equation"
  }
}

Input Schema

NameRequiredDescriptionDefault
amsNoAMS LaTeX for .tex
latexYesLaTeX
confirmNoMust be true to make changes
size_ptNoPer-equation size in pt (menu sizes + 0.1 pt steps)
out_pathYesAbsolute output path
overwriteNoReplace existing file
capture_pngNoOptional .png of the editor
verify_latexNoLaTeX round-trip check

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses almost nothing beyond output formats. It says nothing about the confirm requirement, overwrite semantics, permission/auth needs, or what happens when the file already exists — all material for a mutation tool that writes to an absolute path.

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?

A single dense sentence with the core verb and resource front-loaded and no filler. The format enumeration is long but each token is load-bearing since it defines the accepted extensions.

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

Completeness2/5

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

For an 8-parameter file-writing tool with no annotations and no output schema, the description covers only the format dimension. It omits the confirm gate on mutations, overwrite behavior, and side effects an agent must know before calling it, leaving consequential behavior undocumented.

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?

Schema coverage is 100%, so a baseline of 3 applies, and the description earns above that by adding the rule that output format is derived from the out_path extension and by clarifying that .tex implies LaTeX with ams=true for AMS. It still says nothing about confirm, overwrite, capture_png, or size_pt, leaving the schema to do that work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Render LaTeX with MathMagic to a file') and adds a precise extension-to-format mapping, so the agent knows exactly what the tool produces. It does not name a sibling or explicitly distinguish itself from mathmagic_render_eps or mathmagic_preview_equation, which keeps it short of a 5.

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 rather than stated: an agent can infer this is the tool to use when it needs a LaTeX equation written to disk, and the extension list implicitly guides format choice. There is no explicit when-not guidance, no mention of the confirm gate needed to make changes, and no reference to alternatives such as preview or batch rendering.

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