Skip to main content
Glama
MathMagic MCP Pro

MathMagic MCP Pro

by mrtersn9-cpu

mathmagic_preview_equation

Validates LaTeX, equation marker, and size settings and returns the planned insertion steps without modifying the document, so you can check a formula before placing it in InDesign.

Instructions

Validate LaTeX/marker/size and show the planned steps. No changes.

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>"
    },
    "name": "mathmagic_preview_equation"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNooffline (default; no focus change) or plugin (plugin brings windows to front)
latexYesLaTeX
markerNo[[MM:ID]]
size_ptNoPer-equation size in pt (menu sizes + 0.1 pt steps)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full load and does deliver the most important behavioral fact: the operation is non-mutating. It says nothing about what a validation failure looks like, whether errors are returned inline or thrown, or what "planned steps" contains, so gaps remain for a validation tool.

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?

Two terse fragments, front-loaded with the verb and ending on the safety-critical constraint. Nothing is wasted, though the telegraphic style costs a little readability.

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 four-parameter validation tool with no output schema, the description should say what the preview returns (steps, errors, resolved marker) and whether mode affects validation. It covers the read-only nature but leaves the return behavior unspecified.

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 schema already documents latex, marker, size_pt and the offline/plugin mode enum. The description restates the same three field names without adding format, constraint, or default information beyond the schema, so baseline 3 applies.

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 gives a specific verb ("Validate") tied to specific resources ("LaTeX/marker/size") plus a preview outcome ("show the planned steps"). The trailing "No changes." distinguishes it from mutating siblings like mathmagic_create_equation and mathmagic_edit_equation, though no sibling is named explicitly.

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 changes" implies a dry-run / pre-flight usage, which is meaningful guidance, but the definition never states when to prefer this over mathmagic_create_equation or mathmagic_preview_batch. Usage must be inferred rather than read.

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