Skip to main content
Glama
garuh143

RPG Maker MZ/MV MCP Server

by garuh143

get_skill

Retrieve specific skill data by ID from RPG Maker MZ/MV projects to access game mechanics information for development and integration.

Instructions

Get a specific skill by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
skillIdYesThe ID of the skill to retrieve

Implementation Reference

  • The `getSkill` handler function retrieves a specific skill by its ID from the skills list in the project.
    export async function getSkill(projectPath: string, skillId: number): Promise<Skill | null> {
      const skills = await getSkills(projectPath);
      return skills.find(skill => skill && skill.id === skillId) || null;
    }
Behavior2/5

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

No annotations provided, so description carries full burden. States read operation ('Get') but fails to disclose error behavior (404 vs null), response structure, or whether this retrieves from cache or database.

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?

Extremely concise at 6 words. Front-loaded with verb. No redundant text, though brevity comes at cost of missing behavioral context. Every word earns its place.

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?

Adequate for simple getter with 1 parameter, but gaps remain: no output schema exists, so description should hint at return structure or skill attributes. Domain context (game development) is implied by siblings but not stated.

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?

Schema has 100% coverage describing skillId, so baseline is 3. Description adds no additional parameter semantics (valid ID ranges, format, examples) but doesn't need to compensate given complete schema documentation.

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?

Clear verb (get) + resource (skill) + scope (specific by ID). Distinguishes from sibling get_skills (list) and search_skills (filtered query), though could clarify this is a game/RPG skill given context of create_damage_skill siblings.

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 explicit when-to-use guidance or comparison to alternatives. Lacks guidance on when to use search_skills vs get_skills vs get_skill, or error handling if ID doesn't exist.

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