Skip to main content
Glama
garuh143

RPG Maker MZ/MV MCP Server

by garuh143

create_healing_skill

Generate healing skills for RPG Maker MZ/MV games by defining name, healing formula, MP cost, and target scope to restore character health during gameplay.

Instructions

Create a healing skill (simplified)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesSkill name
healFormulaYesHeal formula (e.g., "a.mat * 3 + 100")
mpCostYesMP cost
scopeYesTarget scope (7=ally all, 11=user)
descriptionNoSkill description

Implementation Reference

  • The handler function that creates a healing skill by calling createSkill with healing-specific damage parameters.
    export async function createHealingSkill(
      projectPath: string,
      name: string,
      healFormula: string,
      mpCost: number,
      scope: number,
      description?: string
    ): Promise<Skill> {
      return await createSkill(projectPath, {
        name,
        description: description || `${name}でHPを回復する`,
        mpCost,
        scope,
        damage: {
          type: 3, // HP recovery
          elementId: 0,
          formula: healFormula,
          variance: 20,
          critical: false
        },
        animationId: 47,
        message1: `%1は${name}を唱えた!`,
        stypeId: 1,
        iconIndex: 72
      });
    }
  • The tool definition and input schema for create_healing_skill.
    {
      name: 'create_healing_skill',
      description: 'Create a healing skill (simplified)',
      inputSchema: {
        type: 'object',
        properties: {
          name: { type: 'string', description: 'Skill name' },
          healFormula: { type: 'string', description: 'Heal formula (e.g., "a.mat * 3 + 100")' },
          mpCost: { type: 'number', description: 'MP cost' },
          scope: { type: 'number', description: 'Target scope (7=ally all, 11=user)' },
          description: { type: 'string', description: 'Skill description' },
        },
        required: ['name', 'healFormula', 'mpCost', 'scope'],
      },
  • src/index.ts:698-706 (registration)
    The registration switch-case that routes the create_healing_skill tool call to the corresponding handler function.
    case 'create_healing_skill':
      return await skillTools.createHealingSkill(
        this.projectPath,
        args.name,
        args.healFormula,
        args.mpCost,
        args.scope,
        args.description
      );
Behavior1/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but reveals nothing about side effects, validation rules, idempotency, or return values. The term '(simplified)' hints at behavioral differences from other tools but provides no specifics.

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 brief with zero redundancy. However, given the tool's complexity (5 parameters, no annotations, no output schema), it may be too concise to be 'appropriately sized' for the information burden required.

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?

For a creation tool with multiple parameters and no output schema or annotations, the description is inadequate. It lacks explanation of what the tool returns, what '(simplified)' implies, how it differs from create_skill, and any error conditions or side effects.

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?

Schema description coverage is 100% (all 5 parameters are documented with types and descriptions, including helpful examples for healFormula and scope values). Since the schema is self-documenting, the description adds no additional parameter semantics, warranting the baseline score of 3.

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 identifies the action ('Create') and resource type ('healing skill'), distinguishing it from sibling tools like create_damage_skill and create_buff_skill. However, the '(simplified)' qualifier is vague and unexplained, leaving ambiguity about its relationship to the generic create_skill tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

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

No usage guidance is provided. The description fails to indicate when to use this tool versus the generic create_skill or other specialized skill creators, and mentions no prerequisites or constraints for invocation.

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