rpgmaker-mz-mcp

Overview Schema Source Related Servers Discussions Admin

create_skill

Create a new RPG Maker MZ skill with custom properties, including damage, effects, costs, scope, and messages; omitted fields fall back to defaults.

Instructions

Create a new skill with custom properties. Omitted fields use new-skill defaults: stypeId 1 (Magic), scope 1, occasion 1 (battle only), hitType derived — 0 certain for recovery or ally/user scopes, else 2 magical for Magic skills, else 1 physical if it deals damage, else 0. An effect referencing a missing record throws: Add/Remove State (code 21/22) → state, Learn Skill (43) → skill, Common Event (44) → common event.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	Skill name
`note`	No	Note field (notetags)
`scope`	No	Target scope (1=enemy single, 2=enemy all, 7=ally all, etc.)
`speed`	No	Speed correction (-2000..2000; positive acts earlier). Default 0
`damage`	No	Damage configuration
`dryRun`	No	Preview only: return a diff of what would change without writing to disk.
`mpCost`	No	MP cost
`tpCost`	No	TP cost
`tpGain`	No	User TP gained on use. Default 0
`effects`	No	Skill effects (buffs, debuffs, states, etc.)
`hitType`	No	0 certain hit, 1 physical (HIT/EVA, counterable), 2 magical (MEV, reflectable). Default derived from stypeId/scope/damage
`repeats`	No	Number of hits (1-9). Default 1
`stypeId`	No	Skill type (0=none — typical for enemy-only skills, not sealed by Silence; 1=magic, 2=special, etc.). Default 1
`message1`	No	Battle message (line 1, %1 = user name)
`message2`	No	Battle message line 2
`occasion`	No	Usable: 0 always, 1 battle only (default), 2 menu only, 3 never
`iconIndex`	No	Icon index (0-1000+)
`animationId`	No	Animation ID
`description`	No	Skill description
`successRate`	No	Success rate percent. Default 100
`requiredWtypeId1`	No	Required weapon type 1 (0=none)
`requiredWtypeId2`	No	Required weapon type 2 (0=none)

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedv1.4.0Sep 28, 2026

addedInput schema / properties / hitType

Added value: +{
+  "description": "0 certain hit, 1 physical (HIT/EVA, counterable), 2 magical (MEV, reflectable). Default derived from stypeId/scope/damage",
+  "maximum": 2,
+  "minimum": 0,
+  "type": "integer"
+}

changedInput schema / properties / message1 / description

Previous value: -"Battle message"New value: +"Battle message (line 1, %1 = user name)"

addedInput schema / properties / message2

Added value: +{
+  "description": "Battle message line 2",
+  "type": "string"
+}

addedInput schema / properties / note

Added value: +{
+  "description": "Note field (notetags)",
+  "type": "string"
+}

addedInput schema / properties / occasion

Added value: +{
+  "description": "Usable: 0 always, 1 battle only (default), 2 menu only, 3 never",
+  "maximum": 3,
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / repeats

Added value: +{
+  "description": "Number of hits (1-9). Default 1",
+  "maximum": 9007199254740991,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / requiredWtypeId1

Added value: +{
+  "description": "Required weapon type 1 (0=none)",
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / requiredWtypeId2

Added value: +{
+  "description": "Required weapon type 2 (0=none)",
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / speed

Added value: +{
+  "description": "Speed correction (-2000..2000; positive acts earlier). Default 0",
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}

changedInput schema / properties / stypeId / description

Previous value: -"Skill type (1=magic, 2=special, etc.)"New value: +"Skill type (0=none — typical for enemy-only skills, not sealed by Silence; 1=magic, 2=special, etc.). Default 1"

addedInput schema / properties / successRate

Added value: +{
+  "description": "Success rate percent. Default 100",
+  "maximum": 100,
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / tpGain

Added value: +{
+  "description": "User TP gained on use. Default 0",
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}

First observedv1.2.0Jul 31, 2026

TDQS

A3.5/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does real work: it spells out default values for omitted fields (stypeId 1, scope 1, occasion 1) and the exact derivation rule for hitType, plus the failure behavior when an effect references a missing record (codes 21/22/43/44). It does not disclose persistence/ID-allocation behavior or how dryRun interacts with the call, which keeps it from a 5.

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?

Front-loaded with the core purpose, then the defaults and error semantics. It is dense and every clause carries information, though the hitType derivation sentence is long and hard to parse on first read.

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?

For a 22-parameter mutation tool with no annotations and no output schema, the description covers defaults and error cases well. It omits what the call returns (e.g., the created skill's id) and gives no information about dryRun outside the schema, leaving gaps for an agent that must reason about the write's outcome.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema by specifying the exact default-derivation algorithm for hitType and the concrete fallback defaults for stypeId/scope/occasion, which the schema only states partially.

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 verb+resource: 'Create a new skill with custom properties.' An agent immediately knows this is the generic skill-creation entry point. However, it never distinguishes itself from the many specialized siblings (create_damage_skill, create_healing_skill, create_buff_skill, create_state_skill, update_skill), so sibling routing is left to inference.

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?

There is no when-to-use or when-not-to-use guidance and no mention of the alternative creator tools. The only contextual information is about field defaults and error conditions, not about selecting this tool over its siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

create_skill

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools