Skip to main content
Glama
garuh143

RPG Maker MZ/MV MCP Server

by garuh143
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_system

Retrieve system data from RPG Maker MZ/MV projects to access game configuration, settings, and metadata for development and management tasks.

Instructions

Get system data

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/tools/systemTools.ts:7-10 (handler)
    The getSystem function reads the 'System.json' file for the given project path, serving as the core handler for the 'get_system' tool.
    export async function getSystem(projectPath: string): Promise<SystemData> {
  const systemPath = getDataPath(projectPath, 'System.json');
  return await readJsonFile<SystemData>(systemPath);
}

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.3/5.0
Behavior2/5

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

The description implies a read operation but provides no details about the nature of 'system data', potential side effects, or output format. Annotations are absent, so the description should carry the burden but fails.

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?

The description is a single sentence, making it concise, but it sacrifices informativeness. It is under-specified, not effectively concise.

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 no output schema and no annotations, the description should explain what the tool returns (e.g., system version, settings). It fails to provide sufficient context for an agent to understand the tool's purpose.

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

Parameters3/5

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

With no parameters, the schema already covers 100%. The description adds no semantic value beyond the verb, but the lack of params means no enhanced meaning is needed. Baseline 4 is reduced because the description could have clarified what 'system data' encompasses.

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 system data' is vague and does not specify what constitutes 'system data' or how it differs from siblings like get_items or get_variables.

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 on when to use this tool vs alternatives (e.g., get_items, get_variables). The description lacks any context about typical use cases.

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

Deploy Server

Other Tools