RPG Maker MZ/MV MCP Server

Overview Schema Source Related Servers Discussions Admin

get_switches

Retrieve all game switch names from RPG Maker MZ/MV projects to manage event triggers and conditional logic in game development.

Instructions

Get all game switch names

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Implementation Reference

src/tools/systemTools.ts:54-57 (handler)

Implementation of the get_switches tool handler.

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Apr 2, 2026

TDQS

B3.4/5.0

Behavior2/5

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

Description only states it gets names. No annotations provided, so the description should disclose behavioral traits (e.g., read-only, authentication, side effects). It lacks depth.

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?

Single sentence, no waste. Very concise, but could include more detail without harming conciseness.

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?

Adequate for a zero-parameter tool, but lacks contextual details like output format or behavior. No output schema or annotations to supplement.

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?

No parameters exist, so the schema covers 100%. Baseline is 4 for zero parameters, and the description does not need to add param info.

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?

Clear verb ('Get') and resource ('all game switch names') define the tool's purpose. It is easily distinguishable from sibling tools like 'get_items' or 'get_map_event'.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. It does not mention any prerequisites, conditions, or when not to use it.

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