Skip to main content
Glama
MathMagic MCP Pro

MathMagic MCP Pro

by mrtersn9-cpu

mathmagic_render_eps

Exports a LaTeX equation as an .eps file at a specified path, with optional PNG capture, LaTeX verification, overwrite control, and confirmation before writing.

Instructions

Alias of mathmagic_export_equation for .eps output.

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_render_eps"
  }
}

Input Schema

NameRequiredDescriptionDefault
latexYesLaTeX
confirmNoMust be true to make changes
size_ptNoPer-equation size in pt (menu sizes + 0.1 pt steps)
out_pathYesAbsolute .eps path
overwriteNoReplace existing file
capture_pngNoOptional .png
verify_latexNoLaTeX check

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations supplied, the description carries the behavioral burden but only implies generation of an EPS artifact. It adds no operational context about file-writing side effects, overwrite risk, confirmation, optional capture or verification, or the expected result; "alias" merely defers those semantics elsewhere.

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?

The single sentence is direct, unambiguous, and free of filler. Its brevity is efficient but overly reliant on the sibling definition for a seven-parameter, file-producing tool.

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 a tool with seven parameters, no annotations, and no output schema, an alias-only description provides limited operational documentation. The schema makes basic invocation possible, but the agent must consult mathmagic_export_equation to understand the actual workflow and side effects.

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 description coverage is 100%, so the baseline is 3 even though the description documents no parameters. The ".eps output" phrase reinforces the fixed format already expressed by out_path but adds no parameter syntax, interactions, or usage details beyond the schema.

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?

The description makes the intended result clear—.eps output produced through the same operation as mathmagic_export_equation—and explicitly identifies that sibling relationship. It does not independently explain the export/render operation, so full purpose clarity depends on consulting the referenced tool.

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

Usage Guidelines4/5

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

The phrase "for .eps output" supplies a clear when-to-use context, while naming mathmagic_export_equation identifies where the canonical behavior is defined. It does not explain when to prefer this alias over the named tool or provide any when-not guidance.

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