Skip to main content
Glama
garuh143

RPG Maker MZ/MV MCP Server

by garuh143

get_game_title

Retrieve the title of an RPG Maker MZ or MV game project to identify and manage game assets within the MCP server.

Instructions

Get the game title

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that retrieves the game title from the system data.
    export async function getGameTitle(projectPath: string): Promise<string> {
      const system = await getSystem(projectPath);
      return system.gameTitle;
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It fails to indicate whether this is a cached read, expensive database lookup, or safe operation. It also omits what format the game title is returned in.

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?

The description is extremely concise at only four words with zero redundancy. While appropriately sized for a simple getter tool, it sacrifices necessary context that would have earned a higher score in other dimensions.

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?

For a parameter-less tool with no output schema, the description is minimally viable but contains clear gaps. It does not explain what the game title represents in the system, nor does it describe the return value format, which would be useful given the lack of output schema.

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 guidelines, zero parameters establishes a baseline score of 4, as there are no parameter semantics to describe beyond what the empty schema conveys.

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 'Get the game title' is a tautology that restates the tool name. While it technically uses a verb and resource, it fails to distinguish from the sibling tool update_game_title or clarify the scope of what 'game title' refers to (e.g., window title vs. internal project 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?

Provides no guidance on when to use this tool versus alternatives. It fails to mention the complementary update_game_title sibling or any prerequisites for retrieving the title.

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