Skip to main content
Glama
MathMagic MCP Pro

MathMagic MCP Pro

by mrtersn9-cpu

mathmagic_dismiss_dialogs

Acknowledge harmless MathMagic font warnings and Tip of the Day dialogs so background equation insertion can continue, while leaving the license dialog untouched. Set confirm to true to make changes.

Instructions

Acknowledge only known harmless MathMagic dialogs (font warning, Tip of the Day). Never the 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_dismiss_dialogs"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoMust be true to make changes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

A4/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 explanatory burden, and it does add real value by disclosing the safety guardrail around the license dialog. However, it does not say what happens to unrecognized dialogs, whether an acknowledgement is irreversible, or whether the call fails or no-ops when the guarded dialog is present — meaningful gaps for an action tool with zero annotation coverage.

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?

Two short clauses with zero filler, and the permitted scope is front-loaded ahead of the prohibition. Every word constrains behavior.

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

Completeness4/5

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

For a one-parameter action tool with no output schema, the definition covers what is acted on and what must never be acted on, which is the essential information. The one remaining gap is that it never ties the action to the required confirm=true flag, so an agent could miss the confirmation gate.

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% and the single 'confirm' boolean is fully documented in the schema ('Must be true to make changes'), so the schema does the work. The description adds nothing about the parameter, leaving the baseline 3; a note that acknowledgement requires confirm=true would have earned a 4.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb/resource pair ('acknowledge ... MathMagic dialogs') and immediately bounds it to a named subset (font warning, Tip of the Day). No sibling tool shares this responsibility, and the enumerated dialog names make the target unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

It states both the when ('known harmless dialogs') and an explicit when-not ('Never the license dialog'), which is the critical routing decision for this tool. It does not name an alternative tool for the license case, but nothing in the sibling list plausibly handles it, so the missing 'alternatives' clause costs little.

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