Skip to main content
Glama
MathMagic MCP Pro

MathMagic MCP Pro

by mrtersn9-cpu

mathmagic_capture_editor

Saves a PNG of the open MathMagic equation window for documentation or review without changing focus, so you can keep working in other apps.

Instructions

Save a PNG of the open MathMagic equation window (PrintWindow, no focus change).

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": {
      "out_png": "<out_png>"
    },
    "name": "mathmagic_capture_editor"
  }
}

Input Schema

NameRequiredDescriptionDefault
out_pngYesAbsolute .png path

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?

With no annotations provided, the description carries the full disclosure burden, and it does add real value by stating 'PrintWindow, no focus change' — telling the agent this capture will not steal focus or disturb the active window. It does not disclose failure behavior with no open window, whether an existing out_png is overwritten, or how multiple equation windows are disambiguated.

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 short sentence, front-loaded with the action and resource, with the mechanism qualifier in parentheses. No filler or redundancy.

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 one-parameter, single-purpose capture tool with no output schema, the definition covers the essential behavior and the notable side-effect profile (no focus change). Only minor gaps remain around preconditions and error/overwrite behavior.

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?

There is a single parameter with 100% schema description coverage ('Absolute .png path'), so the schema already does the documentation work. The description adds no further meaning about the output path, format constraints, or directory requirements, which is the expected baseline-3 outcome here.

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?

States a concrete verb and resource: save a PNG of the open MathMagic equation window. The parenthetical '(PrintWindow, no focus change)' clarifies the mechanism, which distinguishes it from sibling rendering/export tools like mathmagic_render_eps or mathmagic_export_equation, though it never names those alternatives explicitly.

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 only implied: it applies to the currently open equation window, so an agent can infer it should be called while a window is live rather than as a headless export. There is no explicit when-to-use/when-not statement, no routing guidance against the export/render siblings, and no mention of what happens if no window is open.

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