Skip to main content
Glama
MathMagic MCP Pro

MathMagic MCP Pro

by mrtersn9-cpu

mathmagic_launch

Starts the math editor in the background without activating it and reports LICENSE_REQUIRED when an authorization dialog appears, so workflows can initialize without interrupting other applications.

Instructions

Start MathMagic without activating it; reports LICENSE_REQUIRED if the Authorization dialog appears.

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

Input Schema

NameRequiredDescriptionDefault
confirmNoMust be true to make changes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

A3.7/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 burden, and it does disclose two non-obvious behaviors: the app is launched without taking focus, and a LICENSE_REQUIRED condition is surfaced when the Authorization dialog appears. However, it says nothing about what happens if MathMagic is already running, whether the call is idempotent, or what a successful launch returns.

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?

One sentence, front-loaded with the action and immediately followed by the two facts an agent most needs: no activation, and the LICENSE_REQUIRED failure signal. No filler or restatement of the tool name.

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

Completeness5/5

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

For a one-parameter, no-annotation, no-output-schema launch tool, the description covers the essential edge cases: background launch semantics and the license/interaction failure mode. The remaining gaps (idempotency, return shape) are minor relative to the tool's simplicity.

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?

There is a single parameter, confirm, which the schema already describes at 100% coverage ('Must be true to make changes'). The description adds no explanation of when confirm is needed or what it gates, and it slightly muddies the picture by describing a launch operation that presumably changes nothing while the schema implies a guard against changes.

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?

Names a specific verb (Start) and resource (MathMagic) plus a distinguishing behavioral trait: it launches without activating. It does not differentiate from the sibling mathmagic_status, which an agent might reasonably confuse with checking whether MathMagic is running, so it stops short of 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 only implied: 'Start MathMagic' suggests calling this before other MathMagic operations, and 'without activating it' hints at the background-launch scenario. There is no explicit when-to-use, no exclusion, and no reference to alternatives such as mathmagic_status or mathmagic_dismiss_dialogs.

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