Skip to main content
Glama
MathMagic MCP Pro

MathMagic MCP Pro

by mrtersn9-cpu

mathmagic_backup_indd

Copy the last saved InDesign (.indd) document to a backup folder, excluding unsaved changes, to preserve a stable version before making further edits.

Instructions

Copy the last saved .indd to another folder (unsaved changes excluded).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "folder": "<folder>"
    },
    "name": "mathmagic_backup_indd"
  }
}

Input Schema

NameRequiredDescriptionDefault
folderYesAbsolute backup folder
confirmNoMust be true to make changes
documentNoOpen InDesign document name (default: active document)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

B3.4/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 of disclosure and does add one important behavioral fact: only the last saved file is copied, so unsaved edits are excluded. However, it is silent on whether an existing file in the target folder is overwritten, whether the copy is renamed or timestamped, what happens if no document is open, and what the call returns.

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 front-loaded sentence with zero filler; the most decision-relevant constraint (unsaved changes excluded) is placed where it will be read first. Its brevity borders on under-specification, but no wording is wasted.

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?

For a three-parameter file-writing tool with no annotations and no output schema, the definition covers the essential semantic (copy of last saved file) but omits overwrite semantics, failure conditions, and result information that an agent would need to call it safely.

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?

Schema description coverage is 100%, so folder, confirm, and document are already documented in the schema; baseline 3 applies. The description adds only the loose mapping of 'another folder' to the folder parameter and says nothing about the confirm gate or the default-document behavior.

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 uses a specific verb and resource: 'Copy the last saved .indd to another folder.' It also scopes what is copied via '(unsaved changes excluded),' which separates it conceptually from the save sibling. It doesn't explicitly name a sibling alternative, keeping it just 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?

The parenthetical implies the intended use case (back up the on-disk version without committing unsaved edits), but there is no explicit when-to-use versus when-to-save guidance and no statement of alternatives such as mathmagic_save_document. Usage must be inferred.

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