Skip to main content
Glama
MathMagic MCP Pro

MathMagic MCP Pro

by mrtersn9-cpu

mathmagic_create_equation

Insert a native, editable MathMagic equation into an InDesign text frame from LaTeX at an [[MM:ID]] marker without keyboard, mouse, or clipboard, then verify placement and return timing and focus reports.

Instructions

Insert a native MathMagic equation at an [[MM:ID]] marker (no keyboard/mouse/clipboard); returns verification, timing and a focus report. One InDesign undo step (offline).

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

Input Schema

NameRequiredDescriptionDefault
idNoEquation id label (default: marker id)
modeNooffline (default; no focus change) or plugin (plugin brings windows to front)
latexYesLaTeX
markerYes[[MM:ID]]
confirmNoMust be true to make changes
eps_dirNooffline: EPS folder (default: <document>.mathmagic-eps)
replaceNoReplace an existing equation before the marker
size_ptNoPer-equation size in pt (menu sizes + 0.1 pt steps)
documentNoOpen InDesign document name (default: active document)
capture_pngNoOptional .png of the editor
verify_latexNooffline: export LaTeX back and compare structurally (default on; MATHMAGIC_VERIFY_LATEX=0 disables)
remove_markerNoRemove marker after verification

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

A3.5/5.0
Behavior4/5

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

With zero annotations the description carries the full burden, and it does meaningful work: it discloses that insertion is programmatic (no clipboard/UIA input), that the call returns verification, timing, and a focus report, and that offline mode consumes one InDesign undo step, which communicates reversibility. It omits the confirm-gate and what happens when the marker is missing or invalid, keeping it short of a 5.

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 tight sentences with the action and location front-loaded and the side effects (return contents, undo cost) trailing. The heavy parentheticals make it dense, but no clause is filler and nothing is repeated from the schema.

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

Completeness4/5

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

For a 12-parameter mutating tool with no annotations and no output schema, the description covers the essential behavior: how content is placed, what is returned, and the undo/focus cost. The parameter surface is fully documented in the schema, though the confirm requirement and failure modes are left unmentioned in the narrative.

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 all 12 parameters including mode, confirm, verify_latex, and eps_dir. The description only adds the conceptual framing that offline mode is the non-focus-stealing default and that results are verified, which is additive but modest, so the baseline of 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 pairs a specific verb ('Insert') with a specific resource ('native MathMagic equation') and names the exact insertion point ('[[MM:ID]] marker'), which is more precise than the name alone. It does not explicitly contrast itself with the sibling mathmagic_edit_equation or mathmagic_preview_equation, but the verb 'insert' versus 'edit' gives an agent enough to differentiate.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no sibling is named as an alternative. The parenthetical 'no keyboard/mouse/clipboard' hints at a headless workflow but does not tell an agent when to choose this over the edit, preview, or batch tools. Usage must be entirely inferred.

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