Skip to main content
Glama
MathMagic MCP Pro

MathMagic MCP Pro

by mrtersn9-cpu

mathmagic_status

Retrieves read-only status for MathMagic windows, dialogs, InDesign documents, plugin actions, style state, and foreground focus so you can verify the current equation-insertion environment.

Instructions

Read-only: MathMagic windows/documents/dialogs, InDesign documents and plugin actions, style state, foreground.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

C2.9/5.0
Behavior3/5

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

No annotations are supplied, so the description bears the full burden, and it does make one meaningful behavioral claim: the operation is read-only and non-mutating. It also enumerates the domains observed (windows/documents/dialogs, InDesign documents, plugin actions, style state, foreground), which is real behavioral scope. However, it says nothing about what happens if MathMagic or InDesign is not running, whether the call blocks or waits on dialogs, or how the state is returned.

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 extremely short with no filler, but it is a sentence fragment rather than a structured statement, and it lacks a lead clause naming the operation. Brevity here shades into under-specification rather than disciplined concision.

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?

Complexity is low (no params, no nested objects), but there is no output schema and no annotations, so the description is the only source of information about what a status call yields. A comma-separated list of domains is a coarse hint at return contents and leaves the agent unable to predict the response shape or failure behavior.

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 zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description does not need to compensate for any undocumented inputs.

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

Purpose3/5

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

The name plus the fragment 'Read-only: MathMagic windows/documents/dialogs, InDesign documents and plugin actions, style state, foreground' implies a state-snapshot tool covering several domains, but there is no verb or sentence stating that it returns status information. An agent can guess it is a read-only status probe, yet the enumeration of domains is ambiguous about what is actually reported versus merely inspectable. It is distinguishable from action siblings like mathmagic_create_equation or mathmagic_run_batch, but not from peers such as mathmagic_capabilities, mathmagic_preflight or mathmagic_inspect_indesign.

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 when-to-use guidance, no prerequisites, and no mention of alternatives among the many inspection-oriented siblings. The description never says whether to call this before other operations, for diagnostics after a failure, or instead of mathmagic_preflight or mathmagic_capabilities. The 'Read-only' label hints at a safe diagnostic call but does not route the agent.

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