Skip to main content
Glama
MathMagic MCP Pro

MathMagic MCP Pro

by mrtersn9-cpu

mathmagic_apply_styleset

Sets an existing MathMagic StyleSet as the default, for example to restore a backup.

Instructions

Make an existing StyleSet (see get_style) MathMagic's default, e.g. to restore the backup.

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

Input Schema

NameRequiredDescriptionDefault
nameYesStyleSet name
confirmNoMust be true to make changes
make_defaultNoDefault true

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

B3.1/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 burden and discloses little: it does not say that this mutates global editor state, what happens to the previously active StyleSet, whether the change is reversible, or what a failed lookup does. The only added context is the backup-restore example.

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?

One tight sentence with the action front-loaded and the cross-reference and example trailing. No filler, though the extreme brevity leaves the reader wanting one more clause of behavioral detail.

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?

This is an unannotated mutation of a global setting with no output schema, so the description should cover consequences and preconditions. It covers neither, leaving an agent unable to tell what the call changes beyond the literal act of setting a default.

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 coverage is 100%, so confirm and make_default are already documented in the schema and the description rightly does not repeat them. It does add the useful constraint that the name must refer to an existing StyleSet obtainable via get_style, which is a small but real gain.

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: make an existing StyleSet the MathMagic default, and cross-references get_style as the way to find names. It is clear what the tool does, though it does not explicitly distinguish itself from the sibling mathmagic_set_style.

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?

Offers one concrete scenario ("e.g. to restore the backup") and points at get_style for obtaining a valid name. It does not state when not to use it, nor how it differs from set_style, so usage is only implied for other cases.

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