Skip to main content
Glama
garuh143

RPG Maker MZ/MV MCP Server

by garuh143

create_buff_skill

Create buff skills for RPG Maker MZ/MV projects by specifying name, stat type, duration, MP cost, and target scope.

Instructions

Create a buff skill (simplified)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesSkill name
buffTypeYesBuff type (2=ATK, 3=DEF, 4=MAT, 5=MDF, 6=AGI)
turnsYesNumber of turns the buff lasts
mpCostYesMP cost
scopeYesTarget scope (7=ally all, 11=user)
descriptionNoSkill description

Implementation Reference

  • Implementation of the create_buff_skill tool handler.
    export async function createBuffSkill(
      projectPath: string,
      name: string,
      buffType: number,
      turns: number,
      mpCost: number,
      scope: number,
      description?: string
    ): Promise<Skill> {
      return await createSkill(projectPath, {
        name,
        description: description || `${name}で能力を強化する`,
        mpCost,
        scope,
        effects: [
          {
            code: 31, // Add buff
            dataId: buffType,
            value1: turns,
            value2: 0
          }
        ],
        animationId: 52,
        message1: `%1は${name}を使った!`,
        stypeId: 1,
        iconIndex: 73
      });
    }
  • Registration and input schema for create_buff_skill.
    name: 'create_buff_skill',
    description: 'Create a buff skill (simplified)',
    inputSchema: {
      type: 'object',
      properties: {
        name: { type: 'string', description: 'Skill name' },
        buffType: { type: 'number', description: 'Buff type (2=ATK, 3=DEF, 4=MAT, 5=MDF, 6=AGI)' },
        turns: { type: 'number', description: 'Number of turns the buff lasts' },
        mpCost: { type: 'number', description: 'MP cost' },
        scope: { type: 'number', description: 'Target scope (7=ally all, 11=user)' },
        description: { type: 'string', description: 'Skill description' },
      },
      required: ['name', 'buffType', 'turns', 'mpCost', 'scope'],
    },
Behavior2/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. While 'Create' implies a write operation, the description omits whether this returns the created skill ID/object, whether it modifies existing data, or what 'simplified' implies about the creation behavior.

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 single sentence with no redundant words. While brief to the point of under-specification, it efficiently conveys the core purpose without filler content.

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% input schema coverage, the parameter documentation is adequately handled structurally. However, lacking an output schema and annotations, the description should ideally disclose return values or success indicators, which keeps it at minimum viable completeness rather than thorough.

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 all 6 parameters including 'buffType' and 'scope' enums documented in the schema. The description adds no additional parameter context, so it meets the baseline score for complete schema coverage.

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?

States a specific action ('Create') and resource type ('buff skill'), distinguishing it from generic skill creation tools. However, the parenthetical '(simplified)' is unexplained and doesn't clarify when to use this versus siblings like 'create_skill' or 'create_damage_skill'.

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 tool versus alternatives like 'create_skill' or 'create_state_skill'. No mention of prerequisites, constraints, or specific use cases that warrant the 'simplified' approach.

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