Skip to main content
Glama
MathMagic MCP Pro

MathMagic MCP Pro

by mrtersn9-cpu

mathmagic_save_document

Saves an open InDesign document in place when it already has a file, with optional confirmation and target document selection.

Instructions

Save the InDesign document in place (only if it already has a file).

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

Input Schema

NameRequiredDescriptionDefault
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 must carry the safety profile. It does disclose the key constraint that the document must already have a file, which implies the on-disk copy will be overwritten. It does not state that this mutates the file irreversibly, whether a dialog or save prompt may appear, or that the confirm flag gates the operation.

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 sentence with no filler, and the operative constraint sits in a parenthetical immediately after the action. Slightly denser phrasing around the precondition could make it even more scannable, but nothing 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 two-parameter mutation tool with no annotations and no output schema, the definition covers what the tool does and its main precondition but omits mutation consequences and the confirm requirement. That leaves a modest gap an agent must fill from the schema alone.

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 coverage is 100%, so both the confirm flag and the document name are already documented in the schema. The description adds only the scoping condition tied to the document parameter and nothing about confirm semantics, so baseline 3 applies.

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 and resource (save the InDesign document) plus the 'in place' semantics, which distinguishes it from writing to a new path. It does not differentiate itself from close siblings such as mathmagic_backup_indd, so an agent comparing the two must infer which is the backup and which is the overwrite.

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?

'only if it already has a file' is a genuine precondition that implicitly tells the agent when the tool is not applicable (a never-saved document). However, no alternative is named for that failure case, and no guidance is given on when to prefer this over mathmagic_backup_indd or an export path.

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