Skip to main content
Glama
MathMagic MCP Pro

MathMagic MCP Pro

by mrtersn9-cpu

mathmagic_verify_equation

Verifies a native MathMagic equation before a [[MM:ID]] marker, checking link, embedding, plugin recognition, and labels in an InDesign document.

Instructions

Read-only: native MathMagic equation before [[MM:ID]]? Link, embedding, plugin recognition, labels.

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

Input Schema

NameRequiredDescriptionDefault
markerYes[[MM:ID]]
documentNoOpen InDesign document name (default: active document)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

C2.8/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, and it does contribute one meaningful behavioral fact: the operation is 'Read-only'. It also names the four aspects examined, which hints at what the check reports. It does not say whether a mismatch is an error, what form the verdict takes, or anything about the target document's state.

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

Conciseness3/5

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

It is short with no filler, but the telegraphic style ('... before [[MM:ID]]? Link, embedding, plugin recognition, labels.') is under-specified rather than efficiently structured; the question mark and noun-list fragments make the reader reconstruct the sentence.

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 2-parameter read-only tool with full schema coverage this is close to adequate, and the enumerated check list partially substitutes for the absent output schema. What is missing is the result semantics — pass/fail vs. a structured report — which the agent needs since no output schema exists.

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%, with both the marker pattern and the default-to-active-document behavior documented in the schema itself. The description only echoes the [[MM:ID]] marker form and adds no meaning about the document parameter, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description conveys a read-only check against a [[MM:ID]] marker and enumerates what is inspected (link, embedding, plugin recognition, labels), which distinguishes it from mutating siblings like create_equation or edit_equation. However, it never states a clear verb — 'verify' exists only in the tool name — and the fragment 'native MathMagic equation before [[MM:ID]]?' reads as a note rather than a purpose statement.

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 guidance on when to call this instead of inspect_indesign, preflight, or list_equations, and no prerequisites or exclusions are given. The agent must infer the use case entirely from the word 'verify' in the name.

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