Skip to main content
Glama
MathMagic MCP Pro

MathMagic MCP Pro

by mrtersn9-cpu

mathmagic_rerender_equations

Re-renders labelled InDesign equations from stored LaTeX with the current StyleSet and replaces them in place, so style changes are applied without manual edits.

Instructions

Re-render labelled equations from their stored LaTeX with the current StyleSet and replace them in place.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "mathmagic_rerender_equations"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsNo
confirmNoMust be true to make changes
eps_dirNoEPS folder
documentNoOpen InDesign document name (default: active document)
time_budget_sNo
only_style_differsNoOnly equations made with another style (default true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

C2.9/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. It does convey that this is an in-place mutation of existing equation content, but it never mentions that a confirm flag gates the change, that prior equations are overwritten and may need a backup (a sibling exists for that), or how partial failures/time budgets behave.

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 tight sentence with the operation front-loaded and no filler. It is well structured but terse to the point of omitting operational caveats that a mutation tool needs.

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 six-parameter, non-read-only tool with no annotations and no output schema, the definition is thin: it omits the confirm gate, backup recommendation, selection semantics when ids is empty, and expected failure modes. The agent would be able to identify the operation but not call it safely.

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?

At 67% schema coverage the schema documents confirm and only_style_differs, and the description adds the useful hint that the inputs identify 'labelled equations' rendered against the 'current StyleSet'. However, it says nothing about time_budget_s or eps_dir, and doesn't clarify the id/label format or that an empty ids list means all equations.

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 and resource ('Re-render labelled equations') plus its source data ('stored LaTeX') and destination ('replace them in place'), which is enough to distinguish it from read/inspect siblings like mathmagic_list_equations. It stops short of naming the near-neighbors it could be confused with, such as mathmagic_apply_styleset or mathmagic_render_eps.

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 explicit when-to-use or when-not-to-use guidance, and no alternative is named. The only implied context comes indirectly from the 'current StyleSet' and the only_style_differs parameter description, leaving the agent to guess whether this is the right tool after a style change versus render_eps or apply_styleset.

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