Skip to main content
Glama
Xerolo44

RPG Maker MV MCP Server

by Xerolo44

Create healing skill

create_healing_skill

Define a healing skill that restores HP or MP using RPG Maker MV damage formula syntax, with optional removal of status effects from the target.

Instructions

Create a complete healing skill in one call. The formula uses MV damage syntax (a = user), e.g. 'a.mat * 2 + 200'. Heals HP or MP; optionally also removes states (e.g. a cure spell).

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 (default: one ally)
mpCostNo
tpCostNo
formulaYesRecovery formula, e.g. 'a.mat * 2 + 200'
stypeIdNoSkill type id (1 = Magic by default)
occasionNoWhen usable: 0 always, 1 battle only, 2 menu only, 3 never
varianceNo
iconIndexNoIcon sheet index
animationIdNoAnimation id from the Animations database (0 = none, -1 = normal attack)
descriptionNoTwo-line description shown in menus
recoverTypeNohp
removeStatesNoState ids to remove from the target (100% chance), e.g. poison
Behavior2/5

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

No annotations provided, so description carries full burden. It discloses formula syntax and functionality but lacks details on side effects, validation, or error behavior.

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, front-loaded with purpose, no unnecessary words.

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?

No output schema and minimal description for a tool with 14 parameters. Missing explanation of return value, error cases, and parameter interactions.

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?

Adds meaning for formula, recoverType, removeStates beyond schema. However, with 57% schema coverage and 14 parameters, many parameters (scope, costs, etc.) are not explained in description beyond schema defaults.

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?

Description clearly states it creates a complete healing skill with MV damage syntax, healing HP/MP, and removing states. Distinguishes from siblings like create_damage_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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implied usage for healing skills but no explicit guidance on when to use vs alternatives or exclusions.

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