Skip to main content
Glama
garuh143

RPG Maker MZ/MV MCP Server

by garuh143

create_damage_skill

Create damage-dealing skills for RPG Maker games by defining name, damage formula, MP cost, target scope, and elemental properties.

Instructions

Create a damage-dealing skill (simplified)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesSkill name
damageFormulaYesDamage formula (e.g., "a.mat * 4")
mpCostYesMP cost
scopeYesTarget scope (1=enemy single, 2=enemy all)
elementIdNoElement ID (0=none, 2=fire, 3=ice, 4=thunder, etc.)
descriptionNoSkill description

Implementation Reference

  • Implementation of the create_damage_skill tool handler, which creates a new damage-dealing skill in the game project.
    export async function createDamageSkill(
      projectPath: string,
      name: string,
      damageFormula: string,
      mpCost: number,
      scope: number,
      elementId?: number,
      description?: string
    ): Promise<Skill> {
      return await createSkill(projectPath, {
        name,
        description: description || `${name}を使用する`,
        mpCost,
        scope,
        damage: {
          type: 1, // HP damage
          elementId: elementId || 0,
          formula: damageFormula,
          variance: 20,
          critical: true
        },
        animationId: 1,
        message1: `%1は${name}を放った!`,
        stypeId: 1 // Magic
      });
    }
  • src/index.ts:254-275 (registration)
    Registration of the create_damage_skill tool definition in the MCP server.
    {
      name: 'create_damage_skill',
      description: 'Create a damage-dealing skill (simplified)',
      inputSchema: {
        type: 'object',
        properties: {
          name: { type: 'string', description: 'Skill name' },
          damageFormula: { type: 'string', description: 'Damage formula (e.g., "a.mat * 4")' },
          mpCost: { type: 'number', description: 'MP cost' },
          scope: { type: 'number', description: 'Target scope (1=enemy single, 2=enemy all)' },
          elementId: { type: 'number', description: 'Element ID (0=none, 2=fire, 3=ice, 4=thunder, etc.)' },
          description: { type: 'string', description: 'Skill description' },
        },
        required: ['name', 'damageFormula', 'mpCost', 'scope'],
      },
    },
    {
      name: 'create_healing_skill',
      description: 'Create a healing skill (simplified)',
      inputSchema: {
        type: 'object',
        properties: {
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions '(simplified)' but fails to explain what is simplified—whether certain parameters are auto-generated, if this creates fewer database entries, or how it differs from the full create_skill tool. No mention of return values, side effects, or error conditions.

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 single sentence is efficiently structured with the verb front-loaded and zero redundancy. However, given the tool's complexity (6 parameters) and rich sibling context, it is inappropriately brief rather than appropriately 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?

For a creation tool with 6 parameters, no output schema, and zero annotations, the description is incomplete. It fails to explain the return value, what 'simplified' entails, or how it relates to the 4 other skill creation siblings (create_skill, create_healing_skill, etc.).

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 description coverage is 100%, with clear documentation for scope values and damage formula syntax. The description adds no parameter-specific guidance, but the schema adequately documents semantics, making this the baseline score.

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 states a clear verb ('Create') and resource ('damage-dealing skill'), and distinguishes from siblings like create_healing_skill or create_buff_skill. However, it underutilizes the '(simplified)' tag to explain how this differs from the generic create_skill sibling.

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 guidance on when to use this versus create_skill or other skill creation tools. The '(simplified)' qualifier hints at a distinction but fails to specify the criteria for selection (e.g., 'use when you don't need animation or complex effects').

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