Skip to main content
Glama
Xerolo44

RPG Maker MV MCP Server

by Xerolo44

Create damage skill

create_damage_skill

Create a complete damaging skill for RPG Maker MV with one API call. Specify name, formula (e.g., 'a.mat * 4 - b.mdf * 2'), and optional parameters to define damage type, scope, and more.

Instructions

Create a complete damaging skill in one call. The formula uses MV damage syntax where a is the user and b the target, e.g. 'a.mat * 4 - b.mdf * 2' or 'a.atk * 2 - b.def'. Returns the new skill id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
noteNo
scopeNoTarget scope: 1 one enemy, 2 all enemies, 3-6 random enemies (1-4), 7 one ally, 8 all allies, 9 one dead ally, 10 all dead allies, 11 the user
mpCostNo
tpCostNo
tpGainNoTP the user gains on use
formulaYesDamage formula, e.g. 'a.mat * 4 - b.mdf * 2'
hitTypeNoHit type (affects evasion/reflection rules)magical
stypeIdNoSkill type id (1 = Magic by default)
criticalNoCan critically hit
occasionNoWhen usable: 0 always, 1 battle only, 2 menu only, 3 never
varianceNoDamage variance %
elementIdNoElement id from System types (0 = none, -1 = normal attack element)
iconIndexNoIcon sheet index
damageTypeNoWhat the damage hits (drain variants absorb into the user)hp
animationIdNoAnimation id from the Animations database (0 = none, -1 = normal attack)
descriptionNoTwo-line description shown in menus
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses that the tool creates a skill and returns the new skill id, but does not mention validation, error handling, required permissions, or side effects (e.g., is the skill immediately available?). Adequate but not comprehensive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences packed with essential information: creation scope, formula syntax, and return value. No unnecessary words. Front-loaded with the key action.

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?

Given 17 parameters and no output schema, the description covers creation and formula but omits details on error conditions, default values beyond schema, and exact return format (just 'new skill id'). Adequate for experienced users but incomplete for novices.

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?

The description adds meaningful explanation for the formula parameter: 'The formula uses MV damage syntax where `a` is the user and `b` the target,' with examples. For other parameters (76% schema coverage), the description does not add much beyond schema descriptions, but the formula guidance is valuable.

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

Purpose5/5

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

The description clearly states 'Create a complete damaging skill in one call,' specifying the verb (create), resource (damaging skill), and scope (in one call). It distinctively focuses on damage, differentiating from sibling tools like create_healing_skill and create_state_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?

The description provides no explicit guidance on when to use this tool versus alternatives like create_healing_skill or create_state_skill. The only contextual hint is the tool name and mention of 'damage,' but no when-not-to-use or alternative recommendations.

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/Xerolo44/RPG-Maker-MV-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server