RPG Maker MZ/MV MCP Server

by garuh143

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

get_skills

Retrieve all skill data from RPG Maker MZ/MV projects to manage game mechanics and character abilities.

Instructions

Get all skills from the project

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Implementation Reference

src/tools/skillTools.ts:7-10 (handler)

The function that reads and returns all skills from Skills.json.

export async function getSkills(projectPath: string): Promise<Skill[]> {
  const skillsPath = getDataPath(projectPath, 'Skills.json');
  return await readJsonFile<Skill[]>(skillsPath);
}

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Apr 2, 2026

TDQS

A3.9/5.0

Behavior3/5

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

With no annotations, the description carries the full burden of behavioral disclosure. 'Get' implies a read-only operation, and 'all skills' conveys the scope. However, it does not mention return format, potential performance implications, or whether it modifies anything, though the simplicity of the tool makes this acceptable.

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, front-loaded sentence with zero wasted words. It efficiently communicates the tool's purpose without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter, no-output-schema tool, the description is fully complete. It provides all necessary information for an agent to select and invoke the tool correctly, with no ambiguity about what it does.

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 tool has no parameters, so the baseline is 4. The description clarifies that it retrieves all skills, which adds meaning beyond the empty schema by specifying the scope of the result.

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

Purpose5/5

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

The description 'Get all skills from the project' uses a specific verb ('Get') and clearly identifies the resource ('all skills') and scope ('from the project'). This distinguishes it from sibling tools like get_skill (singular) and search_skills (filtered search).

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 search_skills or get_skill. It simply states what it does without specifying exclusions or use cases, leaving the agent to infer usage.

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