Skip to main content
Glama
MathMagic MCP Pro

MathMagic MCP Pro

by mrtersn9-cpu

mathmagic_capabilities

Provides a read-only live inventory of MathMagic menu commands and InDesign plugin actions, classified for automation, to help identify available operations for scripting.

Instructions

Read-only live inventory of ALL MathMagic menu commands and InDesign plugin actions, classified for automation.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does useful work by declaring 'read-only' and 'live' (i.e., not a cached list). It stops short of describing the classification scheme itself, how many commands to expect, or whether the inventory reflects the currently installed MathMagic version.

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 with no filler. Scope, read-only nature, and the automation classification all land in the first clause sequence.

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?

No output schema exists, so the description must imply the return shape, and it only loosely does so via 'inventory ... classified for automation' without saying what fields or grouping the agent will receive. For a discovery tool that is the primary consumer-facing detail, this is a real gap.

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 nothing for the description to disambiguate; baseline 4 applies. The absence of parameters is consistent with a whole-inventory read.

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?

The description names a specific verb-like resource ('live inventory') and scope ('ALL MathMagic menu commands and InDesign plugin actions'), plus a qualifier ('classified for automation'). It is clearly a capability-discovery tool, distinguishable in spirit from mutating siblings like mathmagic_run_batch, though it does not name an alternative explicitly.

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: 'classified for automation' hints you consult it when building or validating automated workflows. There is no explicit when-to-use statement, no exclusion, and no pointer to a sibling such as mathmagic_status for runtime checks.

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