Skip to main content
Glama
garuh143

RPG Maker MZ/MV MCP Server

by garuh143

update_game_title

Modify the title of an RPG Maker MZ/MV game project to reflect changes in your game's name or branding.

Instructions

Update the game title

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYes

Implementation Reference

  • The implementation of the update_game_title tool handler.
    export async function updateGameTitle(projectPath: string, title: string): Promise<void> {
      const system = await getSystem(projectPath);
      system.gameTitle = title;
    
      const systemPath = getDataPath(projectPath, 'System.json');
      await writeJsonFile(systemPath, system);
    }
  • The MCP tool registration and input schema definition.
    name: 'update_game_title',
    description: 'Update the game title',
    inputSchema: {
      type: 'object',
      properties: {
        title: { type: 'string' },
      },
      required: ['title'],
    },
  • src/index.ts:776-778 (registration)
    The switch case that routes the request to the updateGameTitle handler.
    case 'update_game_title':
      await systemTools.updateGameTitle(this.projectPath, args.title);
      return { success: true };
Behavior2/5

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

No annotations are present, so the description must carry full disclosure burden. It fails to mention that this is a destructive overwrite operation, whether the change is immediate, or what authentication/permissions are required.

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

Conciseness3/5

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

While the description is brief (4 words), it is too terse to be useful and represents under-specification rather than efficient communication. The single sentence exists but fails to earn its place by adding value beyond the tool name.

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?

For a mutation tool with no output schema and no annotations, the description provides insufficient context. It does not explain side effects, return values, or the nature of the state change being performed.

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%, and the description does not compensate by explaining the 'title' parameter (e.g., whether it is the new title, max length constraints, or formatting requirements).

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

Purpose3/5

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

The description states the basic action ('Update') and resource ('game title'), but it is extremely minimal and borders on restating the tool name. It lacks specificity about what aspect of the title is being updated or any scope limitations.

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 provided on when to use this tool versus the read-only alternative (get_game_title), or any prerequisites for invoking this mutation operation.

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