Skip to main content
Glama
MathMagic MCP Pro

MathMagic MCP Pro

by mrtersn9-cpu

mathmagic_prepare_offline_batch

Prepare offline batch inputs by writing each manifest LaTeX entry to a marker .tex file in an empty output folder, producing source files only for later processing.

Instructions

Write each manifest LaTeX to .tex in an empty folder (inputs only).

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>",
      "output_dir": "<output_dir>"
    },
    "name": "mathmagic_prepare_offline_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoMust be true to make changes
output_dirYesFolder
manifest_pathYesAbsolute .json path

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and discloses very little: it implies writes occur (files created) and that the target folder must be empty, but says nothing about overwrite behavior, whether the empty-folder requirement is enforced or just advisory, required permissions, or what is returned. For a filesystem-writing tool that needs a confirm flag, that is a substantial gap.

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?

A single tight sentence with the output location front-loaded and the folder constraint attached. It is efficient rather than padded, though its terseness pushes some necessary meaning into ambiguous parentheses.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter write tool with no annotations and no output schema, the description should explain folder preconditions, confirm semantics, and failure modes. It only gestures at the empty-folder rule and '(inputs only)', leaving an agent unable to predict outcomes with confidence.

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?

Schema coverage is 100%, so a 3 is the baseline, and the description genuinely adds meaning: output_dir must be an empty folder, manifest_path holds LaTeX per entry, and output files are named '<marker>.tex'. The only untouched parameter is confirm, whose purpose is already clear from the schema.

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 states a concrete action ('Write each manifest LaTeX to <marker>.tex') and a target ('an empty folder'), so the basic verb+resource is present. However, key terms like 'manifest LaTeX' and '(inputs only)' are jargon that leaves the actual goal (preparing offline batch inputs for later compilation) implicit, and it never distinguishes itself from mathmagic_preview_batch or mathmagic_run_batch.

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?

The parenthetical '(inputs only)' faintly suggests this produces inputs rather than running or previewing a batch, but there is no explicit statement of when to choose this over preview_batch or run_batch. No prerequisites or exclusions are given beyond the empty-folder note.

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