Skip to main content
Glama
garuh143

RPG Maker MZ/MV MCP Server

by garuh143

create_actor

Add a new character to RPG Maker MZ/MV projects by defining name, appearance, stats, and abilities for game development.

Instructions

Create a new actor

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
nicknameNo
profileNo
classIdNo
initialLevelNo
maxLevelNo
characterNameNo
characterIndexNo
faceNameNo
faceIndexNo
battlerNameNo
traitsNo
equipsNo
noteNo

Implementation Reference

  • The createActor handler function that creates a new actor and saves it to Actors.json.
    export async function createActor(
      projectPath: string,
      actorData: Omit<Actor, 'id'>
    ): Promise<Actor> {
      const actors = await getActors(projectPath);
    
      // Find the next available ID
      const maxId = actors.reduce((max, actor) => {
        return actor && actor.id > max ? actor.id : max;
      }, 0);
    
      const newActor: Actor = {
        id: maxId + 1,
        ...actorData
      };
    
      actors.push(newActor);
    
      const actorsPath = getDataPath(projectPath, 'Actors.json');
      await writeJsonFile(actorsPath, actors);
    
      return newActor;
    }
  • The MCP tool schema definition for create_actor.
    name: 'create_actor',
    description: 'Create a new actor',
    inputSchema: {
      type: 'object',
      properties: {
        name: { type: 'string' },
        nickname: { type: 'string' },
        profile: { type: 'string' },
        classId: { type: 'number' },
        initialLevel: { type: 'number' },
        maxLevel: { type: 'number' },
        characterName: { type: 'string' },
        characterIndex: { type: 'number' },
        faceName: { type: 'string' },
        faceIndex: { type: 'number' },
        battlerName: { type: 'string' },
        traits: { type: 'array' },
        equips: { type: 'array' },
  • src/index.ts:664-665 (registration)
    The registration/dispatching logic that calls the createActor handler.
    case 'create_actor':
      return await actorTools.createActor(this.projectPath, args);
Behavior2/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. While 'Create' implies a write operation, the description omits idempotency guarantees, error handling (e.g., duplicate names), side effects, or return value structure.

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

Conciseness2/5

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

At three words, the description is brief, but this reflects under-specification rather than efficient information density. It front-loads nothing useful for parameter interpretation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Grossly inadequate for a 14-parameter object creation tool with no output schema. The description omits the domain model (RPG character system), parameter relationships (e.g., initialLevel vs maxLevel constraints), and return behavior.

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

Parameters1/5

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

Schema description coverage is 0% and the description fails to compensate. Critical game-specific parameters (battlerName, faceIndex, characterIndex, classId) receive no explanation. The description adds zero semantic value beyond the bare schema property names.

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

Purpose2/5

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

The description 'Create a new actor' is a tautology that restates the function name without defining what an 'actor' represents in this game development context (playable character). It fails to distinguish from siblings like update_actor or search_actors.

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 guidance provided on when to use create_actor versus update_actor, or prerequisites for creation. No mention of whether actors can be duplicated or if unique constraints apply.

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