Skip to main content
Glama
garuh143

RPG Maker MZ/MV MCP Server

by garuh143

create_state_skill

Design skills that inflict status effects like poison or sleep in RPG Maker MZ/MV games. Specify success chance, MP cost, and target scope to create balanced combat abilities.

Instructions

Create a state-inflicting skill (poison, sleep, etc.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesSkill name
stateIdYesState ID (4=poison, 5=blind, 6=silence, 8=confusion, etc.)
chanceYesSuccess chance (0.0-1.0)
mpCostYesMP cost
scopeYesTarget scope (1=enemy single, 2=enemy all)
descriptionNoSkill description

Implementation Reference

  • Implementation of the createStateSkill tool, which creates a new skill that adds a state effect.
    export async function createStateSkill(
      projectPath: string,
      name: string,
      stateId: number,
      chance: number,
      mpCost: number,
      scope: number,
      description?: string
    ): Promise<Skill> {
      return await createSkill(projectPath, {
        name,
        description: description || `${name}で状態異常を付与する`,
        mpCost,
        scope,
        effects: [
          {
            code: 21, // Add state
            dataId: stateId,
            value1: chance,
            value2: 0
          }
        ],
        damage: {
          type: 0,
          elementId: 0,
          formula: '0',
          variance: 20,
          critical: false
        },
        animationId: 1,
        message1: `%1は${name}を使った!`,
        stypeId: 1
      });
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It fails to mention that this is a mutating operation, whether it is idempotent, what the return value or success indicators are, or any side effects of skill creation.

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?

The description is extremely concise (6 words) and front-loaded with the action verb. However, given the tool's complexity (6 parameters, no annotations, no output schema), this brevity may be insufficient for agent decision-making.

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?

Despite having well-documented parameters, the description lacks necessary context given the absence of annotations and output schema. For a resource-creation tool, it should disclose what constitutes successful creation, any persistence guarantees, or error conditions.

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?

With 100% schema description coverage, the schema adequately documents all parameters (including helpful enum-like mappings for stateId and scope). The description adds no additional parameter semantics, but none are needed given the comprehensive 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?

The description clearly states the verb (Create) and resource (state-inflicting skill) with specific examples (poison, sleep) that distinguish it from sibling tools like create_damage_skill or create_healing_skill. However, it does not explicitly differentiate 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?

The description provides no explicit guidance on when to use this tool versus alternatives like create_skill (generic) or create_buff_skill. While the examples imply the domain (status effects), there are no when/when-not statements or prerequisites mentioned.

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