Skip to main content
Glama
garuh143

RPG Maker MZ/MV MCP Server

by garuh143

set_switch_name

Assign descriptive names to RPG Maker switches to improve event organization and readability in game development projects.

Instructions

Set a switch name

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
switchIdYes
nameYes

Implementation Reference

  • The handler function that sets the name of a switch in the System.json file.
    export async function setSwitchName(
      projectPath: string,
      switchId: number,
      name: string
    ): Promise<void> {
      const system = await getSystem(projectPath);
      system.switches[switchId] = name;
    
      const systemPath = getDataPath(projectPath, 'System.json');
      await writeJsonFile(systemPath, system);
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It implies a write operation via 'Set' but fails to specify idempotency, error handling (what if switchId is invalid?), return values, or whether this creates a new switch or renames an existing one.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

At three words, the description is technically brief, but this represents under-specification rather than efficient communication. There is no structural prioritization of information because there is virtually no information present.

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

Completeness2/5

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

Given the lack of output schema, annotations, and parameter descriptions, the description provides insufficient context. For a simple two-parameter mutation tool, the single phrase fails to establish domain context (e.g., that switches are boolean game states) or operational expectations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, requiring the description to compensate for undocumented parameters. While 'Set a switch name' loosely maps to the 'name' parameter and implies a target switch, it provides no details on 'switchId' semantics, name constraints, or validation rules.

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

Purpose2/5

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

The description 'Set a switch name' is tautological, merely restating the tool name with slight grammatical variation. While it confirms the domain (switches vs. variables), it fails to distinguish from the sibling tool 'set_variable_name' or clarify what constitutes a 'switch' in this context.

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

Usage Guidelines1/5

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

No guidance provided on when to use this tool versus alternatives, prerequisites (e.g., does the switch need to exist first?), or side effects. The description lacks any conditional logic or workflow positioning.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/garuh143/RPG-MakerMV-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server