Skip to main content
Glama
garuh143

RPG Maker MZ/MV MCP Server

by garuh143

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
NameRequiredDescriptionDefault

No arguments

Implementation Reference

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

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

No annotations provided, so description carries full disclosure burden. It only states 'Get' implying read-only, but doesn't disclose return format, pagination behavior, or whether this includes all skill subtypes (buff/damage/healing/state) suggested by sibling tools. No mention of potential size/performance implications of unfiltered retrieval.

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?

Single sentence, six words, front-loaded with verb. Appropriate length for a zero-parameter list operation with no waste or redundancy.

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?

No output schema and no annotations increases burden on description. While 'Get all skills' covers basic intent, gaps remain: no distinction from sibling query tools, no indication of return structure, and ambiguity about whether 'skills' encompasses all subtypes (buff/damage/healing/state skills) shown in sibling tool names.

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?

Zero parameters exist, so baseline score applies per rubric. Schema coverage is 100% (empty object), requiring no additional parameter description in the description text.

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 uses specific verb 'Get' and resource 'skills' and implies scope with 'all'. However, it doesn't explicitly distinguish from sibling 'get_skill' (singular lookup) or 'search_skills' (filtered queries), which would help clarify exact usage boundaries.

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 vs. 'get_skill' (single lookup) or 'search_skills' (filtered search). No mention of performance implications when retrieving all skills vs. using specific lookup alternatives.

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