Skip to main content
Glama
Sign In
RPG Maker MV MCP Server

RPG Maker MV MCP Server

by Xerolo44
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Create buff/debuff skill

create_buff_skill

Creates a skill that applies parameter buffs or debuffs, letting you configure target scope, duration, costs, and icon for RPG Maker MV database skills.

Instructions

Create a skill that applies parameter buffs and/or debuffs. Parameter ids: 0 Max HP, 1 Max MP, 2 Attack, 3 Defense, 4 M.Attack, 5 M.Defense, 6 Agility, 7 Luck. If only debuffs are given the scope defaults to one enemy, otherwise one ally.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "create_buff_skill"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
noteNo
buffsNoBuffs to add to the target
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
debuffsNoDebuffs to add to the target
stypeIdNoSkill type id (1 = Magic by default)
occasionNoWhen usable: 0 always, 1 battle only, 2 menu only, 3 never
iconIndexNoIcon sheet index
animationIdNoAnimation id from the Animations database (0 = none, -1 = normal attack)
descriptionNoTwo-line description shown in menus

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.1

TDQS

A3.6/5.0
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 usefully discloses the non-obvious default scope behavior and parameter-id mapping, but it does not explain persistence, validation, required project state, or other side effects expected of a create/mutation tool.

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?

The description is front-loaded with the core action, followed by the necessary parameter-id legend and a key default-scope rule. Every sentence adds useful information and there is no filler.

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?

The description covers the most domain-specific gaps, especially parameter ids and scope defaults, which is important given 12 parameters and 67% schema coverage. However, with no annotations and no output schema, it should do more to describe the create/mutation behavior and what the tool returns or persists.

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 moderate at 67%, and the description adds substantial meaning that the schema lacks by mapping parameter ids 0-7 to Max HP, Max MP, Attack, Defense, M.Attack, M.Defense, Agility, and Luck. It also explains the scope default rule, though it does not clarify unrelated parameters such as mpCost, tpCost, or note.

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 gives a specific verb and resource: creating a skill that applies parameter buffs and/or debuffs. This clearly distinguishes it from sibling skill-creation tools such as create_damage_skill, create_healing_skill, and create_state_skill, though it does not name those alternatives explicitly.

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?

Usage is implied by the purpose: use this when creating a buff/debuff skill. The description also gives one important usage rule about default scope when only debuffs are present, but it does not state when to choose this over the sibling skill-creation tools or mention any prerequisites.

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

Deploy Server

Other Tools