Skip to main content
Glama
garuh143

RPG Maker MZ/MV MCP Server

by garuh143

set_variable_name

Assign a descriptive name to a game variable in RPG Maker MZ/MV projects, enabling clear identification and management of variables used for game logic, events, and data tracking.

Instructions

Set a variable name

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
variableIdYes
nameYes

Implementation Reference

  • The implementation of the setVariableName function which updates the variable name in the system data.
    export async function setVariableName(
      projectPath: string,
      variableId: number,
      name: string
    ): Promise<void> {
      const system = await getSystem(projectPath);
      system.variables[variableId] = name;
    
      const systemPath = getDataPath(projectPath, 'System.json');
      await writeJsonFile(systemPath, system);
    }
Behavior1/5

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

No annotations are provided, requiring the description to carry the full burden of behavioral disclosure. It fails to mention whether the operation is destructive, what happens if the variableId doesn't exist, or whether the change is persisted immediately. No side effects, error modes, or permission requirements are documented.

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?

The description is three words, but this represents under-specification rather than efficient conciseness. As noted in the calibration examples, extremely brief descriptions that merely restate the name fail to 'earn their place' by providing actionable information to the agent.

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 zero schema coverage, no annotations, and no output schema, the description is inadequate for a 2-parameter mutation tool. It should at minimum clarify that variableId refers to an existing game variable and that this operation modifies metadata (the display name) rather than the variable's value.

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?

With 0% schema description coverage, the description must compensate by documenting both variableId (which variable to rename) and name (the new name). While 'variable name' loosely hints at the name parameter, it provides no explanation of variableId's role as an identifier, nor format constraints for either parameter.

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 variable name' is essentially a tautology that restates the tool name with spaces added. While it identifies the resource (variable name), it fails to distinguish from siblings like set_switch_name or clarify scope beyond what the function name already provides.

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 explicit guidelines are provided for when to use this tool versus alternatives (e.g., set_switch_name) or prerequisites (such as verifying the variable exists via get_variables). The description implies usage through the verb 'Set' but offers no actionable decision criteria.

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