Skip to main content
Glama
MathMagic MCP Pro

MathMagic MCP Pro

by mrtersn9-cpu

mathmagic_inspect_indesign

Inspect InDesign documents, selections, and MathMagic plugin actions read-only without launching InDesign, enabling safe verification before equation insertion.

Instructions

Read-only InDesign probe (never launches InDesign): documents, selection, MathMagic plugin actions.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden and does deliver the two most important behavioral facts: it is read-only and it never launches InDesign, so there are no side effects on the app lifecycle. It stops short of describing the response shape, error behavior when InDesign is absent, or whether it requires an open document, which matters for a probe with no output schema.

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?

A single compact sentence with the key constraint (read-only, never launches InDesign) front-loaded before the list of probe targets. No filler, though the trailing list is compressed to the point of being slightly ambiguous about what is returned for each target.

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

Completeness3/5

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

The schema is empty and there is no output schema, so the description is the only source of information about results — and it never explains what the probe actually returns for documents, selection, or plugin actions. It is adequate to prevent misuse (no accidental launch) but not complete enough to tell an agent what to expect 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 zero parameters, so there is no parameter semantics for the description to add. Baseline 4 applies; the enumeration of probe targets ('documents, selection, plugin actions') usefully hints at result scope even though it is not parameter-related.

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 ('read-only InDesign probe') and enumerates what it inspects: documents, selection, and MathMagic plugin actions. An agent can tell this is an inspection/state-read tool, distinct from action tools like mathmagic_create_equation or mathmagic_run_batch, though it does not explicitly contrast itself with close siblings such as mathmagic_probe_uia or mathmagic_status.

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?

'Read-only' and 'never launches InDesign' imply a safe pre-flight/state-check usage, so the when-to-use context is inferable. However, no explicit condition or alternative is named — an agent is not told when to prefer this over mathmagic_status or mathmagic_probe_uia, nor what happens if InDesign is not running.

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