Skip to main content
Glama
MathMagic MCP Pro

MathMagic MCP Pro

by mrtersn9-cpu

mathmagic_cleanup_marker

Removes an [[MM:ID]] cleanup marker from an InDesign document, defaulting to removal only when a verified equation precedes it.

Instructions

Remove an [[MM:ID]] marker; by default only if a verified equation precedes it.

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

Input Schema

NameRequiredDescriptionDefault
markerYes[[MM:ID]]
confirmNoMust be true to make changes
documentNoOpen InDesign document name (default: active document)
require_equationNoDefault true

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does disclose the key safety behavior that removal is gated on a preceding verified equation. However, it never states what happens when that condition is unmet (error, no-op, or forced removal), whether the removal is reversible, or what the response looks like for a destructive operation.

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?

One compact sentence with the destructive action front-loaded and the default guard appended. Nothing is wasted, though the terseness comes at the cost of omitting failure behavior rather than being tight prose.

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?

The tool is a mutation with four parameters, no annotations, and no output schema, so the description should clarify failure and side-effect semantics. It covers the core guard condition but leaves the agent guessing about the outcome when no verified equation precedes the marker and about the effect of confirm.

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 all four parameters (marker, confirm, document, require_equation) are already documented in structured data. The description adds only a restatement of the require_equation default and no syntax, format, or interaction detail beyond the schema, making the baseline 3 correct.

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 ("Remove") and a specific resource (an [[MM:ID]] marker), so an agent knows exactly what the tool mutates. It does not differentiate against siblings such as mathmagic_verify_equation or mathmagic_edit_equation, which is the only thing keeping it from 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 explicit guidance on when to call this versus alternatives, nor any when-not condition or prerequisite. The clause "by default only if a verified equation precedes it" describes a behavioral guard rather than steering the agent between tools, and it does not say what to do when the guard fails.

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