Skip to main content
Glama
MathMagic MCP Pro

MathMagic MCP Pro

by mrtersn9-cpu

mathmagic_probe_uia

Performs a read-only UI Automation capability scan of MathMagic and detects modal dialogs to verify accessible automation paths without altering the app.

Instructions

Read-only UI Automation capability scan of MathMagic with modal-dialog detection.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

B3.3/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 disclosure burden, and it does state 'read-only' (the key safety property) and that it performs modal-dialog detection, which hints at a known UI-automation blocker. It says nothing about whether the scan attaches to a running MathMagic instance, how long it takes, or what a modal-dialog finding means for the caller, so meaningful gaps remain.

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?

A single front-loaded sentence that states modality (UI Automation), safety (read-only), object (MathMagic), and the special feature (modal-dialog detection) with no filler. Every clause earns its place.

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?

There is no output schema and no annotations, so the description is the only source of truth about what a 'capability scan' actually reports and how the modal-dialog signal is surfaced. For a diagnostic tool whose value is entirely in its result shape, that omission leaves the agent guessing about what it gets back.

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?

The tool takes no parameters, so there is no parameter semantics to explain; the baseline for a zero-param tool applies. The description correctly implies no input is required.

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 and resource: a read-only UI Automation capability scan of MathMagic, plus modal-dialog detection as a distinguishing feature. An agent can tell this is an introspection/probe operation rather than a mutation. It does not, however, differentiate itself from the sibling mathmagic_capabilities, which plausibly overlaps.

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?

There is no guidance on when to run this probe, when not to, or which alternative (e.g. mathmagic_capabilities, mathmagic_status, mathmagic_preflight) covers a similar need. The agent must infer the calling context entirely from the name and one-line description.

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