Skip to main content
Glama
MathMagic MCP Pro

MathMagic MCP Pro

by mrtersn9-cpu

mathmagic_list_equations

Lists MathMagic equations in an InDesign document with IDs, page, embedded status, and style, and can return stored LaTeX for review.

Instructions

Read-only inventory of MathMagic equations in a document (ids, page, embedded, style, optional LaTeX).

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

Input Schema

NameRequiredDescriptionDefault
deepNoAlso ask the plugin about unknown EPS links (slower)
documentNoOpen InDesign document name (default: active document)
include_latexNoReturn stored LaTeX

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it does usefully declare the operation is read-only (no mutation of the document) and discloses the shape of the returned inventory. It says nothing about failure modes when the document is closed, the cost/slowness trade-off of probing unknown EPS links, or whether LaTeX availability depends on stored data.

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?

One sentence, front-loaded with the read-only inventory framing and followed by a compact parenthetical listing return fields. Nothing is redundant or padded.

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 zero-required-parameter read tool with no output schema, the description compensates well by enumerating the returned fields, which is the main thing an agent would otherwise lack. The remaining gap is the deep parameter's behavioral cost, which is only documented in the schema.

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. The description's 'optional LaTeX' corroborates the include_latex flag, but it adds no meaning for the document parameter and never mentions the deep flag, which is the least self-explanatory of the three.

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 ('Read-only inventory of MathMagic equations in a document') and enumerates the fields returned (ids, page, embedded, style, LaTeX), which distinguishes it from mutation siblings such as mathmagic_edit_equation or mathmagic_rerender_equations. It stops short of naming an alternative explicitly, so a 4 rather than 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 Guidelines3/5

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

Usage is implied rather than stated: 'read-only inventory' signals a discovery/listing step before edit, rerender, or export operations. There is no explicit when-to-use framing, no mention of prerequisites (e.g. the plugin must be reachable in InDesign), and no guidance on which sibling to choose when the goal is not a listing.

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