Skip to main content
Glama
garuh143

RPG Maker MZ/MV MCP Server

by garuh143

update_item

Modify properties of an item in your RPG Maker MZ/MV project. Specify the item ID and the changes to apply.

Instructions

Update an item's properties

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemIdYes
updatesYes

Implementation Reference

  • The handler function `updateItem` that performs the logic of reading the item list, updating the specified item, and writing the changes back to Items.json.
    export async function updateItem(
      projectPath: string,
      itemId: number,
      updates: Partial<Item>
    ): Promise<Item> {
      const items = await getItems(projectPath);
      const itemIndex = items.findIndex(item => item && item.id === itemId);
    
      if (itemIndex === -1) {
        throw new Error(`Item with ID ${itemId} not found`);
      }
    
      items[itemIndex] = { ...items[itemIndex], ...updates };
    
      const itemsPath = getDataPath(projectPath, 'Items.json');
      await writeJsonFile(itemsPath, items);
    
      return items[itemIndex];
    }
  • src/index.ts:341-351 (registration)
    Registration of the `update_item` tool definition in the MCP server.
      name: 'update_item',
      description: 'Update an item\'s properties',
      inputSchema: {
        type: 'object',
        properties: {
          itemId: { type: 'number' },
          updates: { type: 'object' },
        },
        required: ['itemId', 'updates'],
      },
    },
  • The switch case in `executeToolFunction` that delegates the `update_item` tool call to `itemTools.updateItem`.
    case 'update_item':
      return await itemTools.updateItem(this.projectPath, args.itemId, args.updates);
Behavior2/5

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

Without annotations, the description carries the full burden of behavioral disclosure. While 'Update' implies mutation, the description lacks critical details: whether updates are partial or full replacement, what happens if the itemId doesn't exist, whether the operation is idempotent, or what properties are valid within the 'updates' object.

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

Conciseness3/5

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

The description is extremely brief at four words. While not verbose, it is under-specified rather than efficiently structured. In this case, greater length would be necessary to document the behavioral contract and parameter semantics that are currently missing.

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 an update operation with a schemaless 'updates' object parameter and no output schema or annotations, the description is inadequate. It must explain valid update fields, error conditions, and return value structure, none of which are present.

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 completely fails to compensate. Neither parameter (itemId, updates) is explained. The description doesn't clarify that itemId expects a numeric identifier, nor what structure/keys are expected in the nested 'updates' object, leaving the caller to guess at valid property names and types.

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 'Update an item's properties' is essentially a tautology that restates the tool name (update_item) with minimal elaboration. While it identifies the resource type as 'item', it fails to distinguish from sibling update tools (update_actor, update_skill, etc.) or define what an 'item' represents in this game system context.

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 guidelines are provided. There is no mention of prerequisites (e.g., whether the item must exist), when to prefer this over create_ methods, error handling behavior for invalid itemIds, or how to use the generic 'updates' object.

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