RPG Maker MZ/MV MCP Server

Overview Schema Source Related Servers Discussions Admin

get_variables

Retrieve all variable names from RPG Maker MZ/MV projects to manage game data and configure events, items, and actors within the MCP server.

Instructions

Get all game variable names

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Implementation Reference

src/tools/systemTools.ts:31-34 (handler)

The implementation of the get_variables tool which retrieves the variables list from the System.json file.

export async function getVariables(projectPath: string): Promise<string[]> {
  const system = await getSystem(projectPath);
  return system.variables;
}

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Apr 2, 2026

TDQS

A4.3/5.0

Behavior3/5

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

No annotations are provided, so the description carries full burden; it only states 'Get all game variable names' without detailing read-only nature or response format, which is adequate but not explicit.

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 a single sentence with zero waste, front-loading the key action and resource.

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

Completeness5/5

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

Given the tool's simplicity (no parameters, no output schema), the description is complete enough for an agent to understand its purpose and use.

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?

There are no parameters, and schema coverage is 100%. The baseline for zero-parameter tools is 4, and the description adds no parameter-specific information beyond the schema.

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 'Get all game variable names' clearly states the verb ('get') and resource ('game variable names'), distinguishing it from sibling tools like get_items or get_switches.

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

Usage Guidelines4/5

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

The description is straightforward and implies a simple retrieval; no explicit when-not or alternatives are needed due to the tool's simplicity, but there is no exclusion guidance.

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