Skip to main content
Glama
garuh143

RPG Maker MZ/MV MCP Server

by garuh143

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
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • 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;
    }
Behavior3/5

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

With no annotations provided, the description carries the full burden. It adds valuable behavioral context by specifying 'names' (indicating it returns identifiers rather than values or objects) and 'all' (indicating no filtering). However, it omits return format, pagination behavior, and error conditions.

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, four-word sentence that is appropriately front-loaded with the action. For a zero-parameter getter tool, this length is optimal with no wasted words.

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?

Given the low complexity (no parameters, simple read operation) and lack of output schema, the description is minimally viable. It adequately explains the operation but should ideally describe the return structure (e.g., array vs object) since no output schema is available to document it.

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?

The input schema contains zero parameters. According to the scoring rubric, this establishes a baseline of 4. The description appropriately does not invent parameter semantics where none exist.

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

Purpose4/5

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

The description clearly states the verb ('Get') and resource ('game variable names') with scope ('all'). However, 'Get' is slightly less specific than 'List' or 'Retrieve', and while the resource distinguishes it from siblings like get_switches, it doesn't explicitly clarify the relationship to set_variable_name.

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?

The description provides no guidance on when to use this tool versus alternatives such as get_switches or set_variable_name. It lacks prerequisites (e.g., whether a game must be loaded first) and exclusion 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