Skip to main content
Glama
MathMagic MCP Pro

MathMagic MCP Pro

by mrtersn9-cpu

mathmagic_place_eps

Places a MathMagic EPS file inline in an InDesign text frame at a [[MM:ID]] marker, with fit, embed and Default Baseline options, as one undoable step.

Instructions

Place a MathMagic EPS inline at [[MM:ID]] (fit, embed, Default Baseline, label) as one undo step.

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": {
      "eps_path": "<eps_path>",
      "marker": "<marker>"
    },
    "name": "mathmagic_place_eps"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoEquation id label
embedNoEmbed (default true)
markerYes[[MM:ID]]
confirmNoMust be true to make changes
replaceNoReplace an existing equation
documentNoOpen InDesign document name (default: active document)
eps_pathYesAbsolute .eps path
remove_markerNoRemove marker after verification
default_baselineNoDefault Baseline (default true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose one genuinely valuable trait: the placement is atomic ('as one undo step'). It says nothing about permissions, what happens if the marker is missing, whether an existing equation is overwritten by default, or how the confirm gate behaves, leaving several mutation-related behaviors unexplained.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with zero filler; the action and its targets come first and the atomicity note closes it. Nothing is redundant or padded.

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 nine-parameter mutating tool with no annotations and no output schema, one sentence is thin, but the fully documented schema compensates for most of it. What remains unaddressed is the confirm prerequisite and the marker/replace/remove_marker interaction, which the agent would need in order to 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?

Schema coverage is 100%, so the baseline is 3; every one of the nine parameters already has its own description. The parenthetical '(fit, embed, Default Baseline, label)' loosely echoes parameter names but adds no syntax, format, or interaction detail (e.g. how replace and marker interact) 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 names a specific verb and resource ('Place a MathMagic EPS inline at [[MM:ID]]') and adds scope detail (fit, embed, Default Baseline, label). It distinguishes the action from render/create/export siblings implicitly, but never explicitly contrasts against them, so it falls 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 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, no mention of prerequisites (e.g. does a document need to be open, must a MathMagic EPS already exist), and no named alternative such as render_eps or edit_equation. The agent must infer the workflow context entirely from the tool name.

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