Skip to main content
Glama
MathMagic MCP Pro

MathMagic MCP Pro

by mrtersn9-cpu

mathmagic_set_style

Create a named MathMagic StyleSet with custom fonts, back up the previous default, set it active, and verify rendering with a probe.

Instructions

Create a StyleSet (font for text/function/variable/vector/number, base size pt, italic variables) from the current default, back up the old default as a StyleSet, make it MathMagic's default and verify with a probe render.

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

Input Schema

NameRequiredDescriptionDefault
fontNoMain font family
nameYesStyleSet name
confirmNoMust be true to make changes
size_ptNo
overwriteNoReplace a StyleSet with the same name
greek_fontNoFont for Greek
number_fontNoFont for numbers
make_defaultNoDefault true
variable_fontNoFont for variables
variable_italicNoItalic variables

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses three side effects an agent could not otherwise predict — the old default is preserved as a backup StyleSet, the new one becomes the global MathMagic default, and a probe render verifies the result. It omits the guardrail that confirm must be true before changes occur and says nothing about rollback if the probe render fails.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The text is a single dense run-on sentence packing four distinct operations (create, back up, set default, verify) into one clause chain. Nothing is wasted, but the sequential behavior would be far easier to act on if broken into ordered steps rather than comma-linked clauses.

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 10-parameter mutating tool with no annotations and no output schema, the description covers the important side effects but leaves gaps: the confirm requirement, overwrite semantics for name collisions, and what a failed probe render implies for the backup/default swap are all absent. Adequate to attempt the call, but not complete for a state-changing tool.

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 90%, so the baseline is 3, and the description adds only marginal meaning on top: it clarifies that size is in points and that variables can be italic, and it groups the font parameters by role (text/function/variable/vector/number). Those groupings do not map cleanly onto the actual parameters (greek_font is unmentioned, and a 'vector' font has no parameter), so the added value is limited and slightly imprecise.

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 concrete verb and resource ('Create a StyleSet') and enumerates what the StyleSet contains. It also reveals the multi-step sequence (back up old default, make default, probe render), which meaningfully distinguishes it from read-oriented siblings like mathmagic_get_style and from mathmagic_apply_styleset. It stops short of naming any sibling explicitly, which keeps it off 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the action sequence: use this when you want a new StyleSet built from the current default and installed as the MathMagic default. There is no explicit when-not guidance, no mention that existing styles can be replaced (the overwrite flag) or that confirmation is required, and no routing to alternatives such as applying an existing StyleSet.

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