Skip to main content
Glama
MathMagic MCP Pro

MathMagic MCP Pro

by mrtersn9-cpu

mathmagic_preflight

Verifies files, pywin32, InDesign and MathMagic responsiveness, and license dialogs before inserting LaTeX equations, so setup problems are caught before any work begins.

Instructions

Read-only readiness check (files, pywin32, InDesign/MathMagic running and responsive, license dialog).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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, the description carries the full burden of behavioral disclosure. It usefully declares that the check is read-only and lists what it checks, including the license dialog, but it does not explain what happens on failure, whether any dialog interaction occurs, or how results are reported.

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?

The definition is a single efficiently structured sentence with the key read-only constraint and checked resources front-loaded. Every element earns its place and there is no redundant wording.

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 zero-parameter readiness check, the description identifies what is checked but does not explain result interpretation or failure behavior. Since there is no output schema and no annotations, the definition is adequate but leaves meaningful gaps about how an agent should act on the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter meaning to add beyond the schema. The schema is empty and fully covered, making a baseline score of 4 appropriate.

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 states a specific operation—a read-only readiness check—and enumerates the resources checked: files, pywin32, InDesign/MathMagic running and responsive, and the license dialog. This is clear enough to distinguish it from a general status or inspection tool, though it does not explicitly name sibling alternatives.

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 by the term 'preflight' and the readiness-check framing, suggesting it should be run before MathMagic operations. However, it does not explicitly say when to use this versus mathmagic_status, mathmagic_capabilities, or mathmagic_inspect_indesign, nor does it state any exclusions.

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