Skip to main content
Glama
Sign In
RPG Maker MV MCP Server

RPG Maker MV MCP Server

by Xerolo44
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Restore backup

restore_backup

Restore one RPG Maker MV project file or every file from a backup session to undo unwanted changes; the current state is backed up first, and the RPG Maker editor must be closed.

Instructions

Restore project files from a backup session (see list_backups). Restores one file (project-relative path like 'data/Actors.json') or, with no file given, every file in the session. The current state is itself backed up first, so a restore can be undone. Refused while a changeset is open (commit or discard it first). The RPG Maker editor must stay closed while files are restored.

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": "restore_backup"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNoProject-relative file to restore; omit to restore all files in the session
sessionNoBackup session name from list_backups; defaults to the most recent

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses that the current state is backed up first so a restore can be undone, that the operation is refused during an open changeset, and that the editor must stay closed. It does not cover return values or partial-failure behavior, which are minor gaps for a restore operation with clear safety semantics.

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?

The description is four compact sentences with zero waste. The most important scoping details (what is restored, reversibility, and blocking conditions) are front-loaded.

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

Completeness4/5

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

Given no annotations and no output schema, the description covers the key behavioral facts needed to call the tool correctly: restore scope, reversibility, changeset conflict, and editor-state prerequisite. It stops short of explaining what a successful return looks like or how partial failures are reported, but it is otherwise complete for invocation.

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?

Schema description coverage is 100%, so the schema already defines both parameters. The description adds useful meaning beyond the schema by giving a concrete project-relative path example ('data/Actors.json') and reinforcing that omitting the file restores the whole session and that the session defaults to the most recent.

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

Purpose5/5

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

The description states a specific verb (Restore) and resource (project files from a backup session), and explicitly cross-references list_backups to distinguish the lookup from the restore action. An agent can tell exactly what this tool does without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit conditions for use: restores one file or all files when no file is given, is refused while a changeset is open (with the remedy to commit or discard first), and requires the RPG Maker editor to be closed. These are concrete when-to-use and when-not-to-use guards rather than implied usage.

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

Deploy Server

Other Tools