Skip to main content
Glama
garuh143

RPG Maker MZ/MV MCP Server

by garuh143

update_actor

Modify RPG Maker MZ/MV actor properties like stats, traits, and parameters by specifying the actor ID and desired changes.

Instructions

Update an actor's properties

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actorIdYesThe ID of the actor to update
updatesYesObject containing properties to update

Implementation Reference

  • The handler function that performs the actual update of the actor data in the JSON storage.
    export async function updateActor(
      projectPath: string,
      actorId: number,
      updates: Partial<Actor>
    ): Promise<Actor> {
      const actors = await getActors(projectPath);
      const actorIndex = actors.findIndex(actor => actor && actor.id === actorId);
    
      if (actorIndex === -1) {
        throw new Error(`Actor with ID ${actorId} not found`);
      }
    
      actors[actorIndex] = { ...actors[actorIndex], ...updates };
    
      const actorsPath = getDataPath(projectPath, 'Actors.json');
      await writeJsonFile(actorsPath, actors);
    
      return actors[actorIndex];
    }
  • src/index.ts:122-123 (registration)
    The definition and registration of the update_actor tool in the tool list.
    name: 'update_actor',
    description: 'Update an actor\'s properties',
  • The input schema definition for the update_actor tool.
    inputSchema: {
      type: 'object',
      properties: {
        actorId: {
          type: 'number',
          description: 'The ID of the actor to update',
        },
        updates: {
          type: 'object',
          description: 'Object containing properties to update',
        },
      },
Behavior2/5

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

No annotations are provided, and the description fails to disclose mutation behavior details: whether updates are partial (merging) or complete replacement, error handling for invalid actorIds, or whether the operation is idempotent. The term 'Update' implies mutation but lacks safety context.

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 a single, efficient sentence with no redundant words. However, given the complexity of nested object updates and mutation behavior, it is under-specified rather than optimally concise.

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 mutation tool with nested object parameters and no output schema, the description is incomplete. It omits what properties are valid within the updates object, whether partial updates are supported, and what error conditions to expect.

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%, with both actorId and updates parameters adequately described in the schema. The description adds no additional parameter semantics, but the schema carries the load appropriately.

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

Purpose3/5

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

The description states the tool updates an actor's properties, which is clear but generic. It does not differentiate from sibling update tools (update_item, update_skill, etc.) or specify what constitutes 'properties' in this context.

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?

No guidance provided on when to use this versus create_actor (for new actors) or get_actor (to check current state). No mention of prerequisites like verifying actor existence before updating.

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