Skip to main content
Glama
MathMagic MCP Pro

MathMagic MCP Pro

by mrtersn9-cpu

mathmagic_preview_batch

Validate a JSON manifest of up to 5000 equations, including optional per-item size_pt, before batch processing. Confirms input without making any changes.

Instructions

Validate a JSON manifest (up to 5000 equations; optional per-item size_pt). No changes.

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": {
      "manifest_path": "<manifest_path>"
    },
    "name": "mathmagic_preview_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
manifest_pathYesAbsolute .json path

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

A3.5/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 disclose the essential trait that nothing is modified, plus an item-count ceiling of 5000, but it never explains what happens on an invalid manifest (thrown error vs. returned error list), whether the file must exist, or any permission or timeout behavior.

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?

The definition is one short, front-loaded fragment with the action first and constraints in a parenthetical, so no sentence is wasted. It is telegraphic to the point of being slightly cryptic, but nothing extraneous is present.

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 one-parameter tool this is nearly enough, but with no annotations and no output schema the description should say what validation produces (a pass/fail result, a list of offending items) and whether an invalid manifest causes a call-level error. Those omissions are the main gap.

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?

There is a single parameter and the schema already documents it at 100% coverage as an absolute .json path, which sets the baseline at 3. The description still adds real meaning the schema does not give: the file is a manifest of equations, it may contain per-item size_pt values, and it is capped at 5000 entries.

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 gives a specific verb and resource combination, 'Validate a JSON manifest', and adds scope detail (up to 5000 equations, optional per-item size_pt). It stands apart from the sibling tools that actually run batches because the final clause 'No changes.' marks it as a validation-only step, though it never names the alternatives it differs from.

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?

'No changes.' implies this is a safe dry run that would precede mathmagic_run_batch or mathmagic_prepare_offline_batch, so an agent can infer a check-then-execute workflow. But no explicit when, when-not, or named alternative is stated, leaving the routing between preview and execution tools to inference.

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