Skip to main content
Glama
garuh143

RPG Maker MZ/MV MCP Server

by garuh143

create_skill

Create custom skills for RPG Maker MZ/MV games by defining properties like name, description, costs, damage formulas, effects, and animations.

Instructions

Create a new skill with custom properties

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesSkill name
descriptionNoSkill description
iconIndexNoIcon index (0-1000+)
mpCostNoMP cost
tpCostNoTP cost
scopeNoTarget scope (1=enemy single, 2=enemy all, 7=ally all, etc.)
damageNoDamage configuration
effectsNoSkill effects (buffs, debuffs, states, etc.)
animationIdNoAnimation ID
message1NoBattle message
stypeIdNoSkill type (1=magic, 2=special, etc.)

Implementation Reference

  • The implementation of `createSkill` in `src/tools/skillTools.ts` handles the creation of a new skill, calculates the next available ID, sets default values, and writes the updated skills list to `Skills.json`.
    export async function createSkill(
      projectPath: string,
      skillData: {
        name: string;
        description?: string;
        iconIndex?: number;
        mpCost?: number;
        tpCost?: number;
        scope?: number;
        damage?: {
          type: number;
          elementId: number;
          formula: string;
          variance?: number;
          critical?: boolean;
        };
        effects?: Array<{
          code: number;
          dataId: number;
          value1: number;
          value2: number;
        }>;
        animationId?: number;
        message1?: string;
        stypeId?: number;
      }
    ): Promise<Skill> {
      const skills = await getSkills(projectPath);
    
      // Find the next available ID
      const maxId = skills.reduce((max, skill) => {
        return skill && skill.id > max ? skill.id : max;
      }, 0);
    
      const newSkill: Skill = {
        id: maxId + 1,
        name: skillData.name,
        description: skillData.description || '',
        iconIndex: skillData.iconIndex || 64,
        mpCost: skillData.mpCost || 0,
        tpCost: skillData.tpCost || 0,
        tpGain: 0,
        scope: skillData.scope || 1, // Default: enemy single
        occasion: 1, // Battle only
        speed: 0,
        successRate: 100,
        repeats: 1,
        hitType: skillData.damage?.type === 1 || skillData.damage?.type === 5 ? 1 : 2,
        animationId: skillData.animationId || 0,
        damage: {
          type: skillData.damage?.type || 0,
          elementId: skillData.damage?.elementId || 0,
          formula: skillData.damage?.formula || '0',
          variance: skillData.damage?.variance !== undefined ? skillData.damage.variance : 20,
          critical: skillData.damage?.critical !== undefined ? skillData.damage.critical : false
        },
        effects: skillData.effects || [],
        message1: skillData.message1 || '',
        message2: '',
        note: '',
        stypeId: skillData.stypeId || 1, // Default: Magic
        requiredWtypeId1: 0,
        requiredWtypeId2: 0,
        messageType: 1,
        traits: []
      };
    
      skills.push(newSkill);
    
      const skillsPath = getDataPath(projectPath, 'Skills.json');
      await writeJsonFile(skillsPath, skills);
    
      return newSkill;
    }
Behavior2/5

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

No annotations provided, so description carries full burden. States 'Create' but omits critical mutation details: persistence model, ID generation, collision handling (duplicate names), or side effects. No disclosure of default values for optional parameters.

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?

Single sentence is efficient and front-loaded, though arguably undersized for an 11-parameter mutation tool with complex nested objects. No redundant information.

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?

With 100% schema coverage, basic parameter documentation is satisfied. However, lacks ecosystem context: doesn't explain relationship to stypeId system, damage formula syntax, or how created skills integrate with actors/items. No output schema compounds the gap.

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% description coverage with detailed examples (damage formulas, scope IDs), so baseline is 3. Description adds 'custom properties' which loosely maps to the flexible schema, but provides no additional syntax guidance, value ranges, or cross-parameter relationships beyond schema.

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

Purpose3/5

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

States verb (Create) and resource (skill) clearly, but fails to distinguish from specialized siblings (create_damage_skill, create_healing_skill, etc.) that likely cover common use cases. 'Custom properties' is vague given the domain-specific parameters available.

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 generic tool versus the specialized skill creators (create_buff_skill, create_state_skill, etc.). No mention of prerequisites, uniqueness constraints, or failure conditions.

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