Skip to main content
Glama

update_database_entry

DestructiveIdempotent

Partially update any RPG Maker database entry by overwriting specific fields, with special append methods for common events and troops. Fetch current values first to enable safe reverts.

Instructions

Partially update an existing database entry: only the keys in fields are overwritten (arrays like traits/learnings/actions are replaced wholesale, not merged); the data file is written immediately and there is no undo, so fetch current values with query_database first if you may revert. Returns the full entry after the update. Fails with an error if the ID does not exist. Special append forms that do not need fields: common_events + appendCommand inserts one event command before the list terminator; troops + addEnemyId adds a member at an auto-computed battle position. Plain troop updates and animations are not supported. Class params in fields accept 8 seeds (expanded to full curves) or 8 arrays of 100 per-level values. Editing tilesets affects every map using them; malformed flags break passability project-wide.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
entityYesWhich database contains the entry
idYesID of the entry to modify (must exist; find it with query_database)
fieldsNoSubset of properties to overwrite, e.g. {"name": "Hero", "price": 250}. Not needed when using appendCommand/addEnemyId
appendCommandNocommon_events only: one event command {code, indent, parameters} appended before the terminator. Common codes: 101+401=Show Text, 121=Control Switches, 122=Control Variables
addEnemyIdNotroops only: enemy ID to append as a new member at an auto-computed screen position
Behavior5/5

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

Discloses multiple behavioral traits beyond annotations: partial update with array replacement, immediate write with no undo, error on missing ID, special append operations, class parameter handling, and side effects of editing tilesets. No contradiction with annotations.

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 lengthy but every sentence adds necessary detail. It front-loads the main purpose and then logically covers nuances. Minor room for trimming, but well-structured overall.

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

Completeness5/5

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

Covers return value (full entry after update), error conditions (ID not existing, unsupported updates), and provides sufficient detail for the 5-parameter, nested-object input. No output schema needed.

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

Parameters5/5

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

Schema has 100% parameter description coverage, but the description adds meaning: clarifies fields behavior (overwrites only given keys, arrays replaced), explains append operations and their parameters, and adds context for class params (seeds or full curves).

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

Purpose5/5

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

The description clearly states it partially updates an existing database entry, specifying that only keys in 'fields' are overwritten and arrays are replaced wholesale. It distinguishes from sibling tools like create_database_entry and delete_database_entry by focusing on update behavior.

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

Usage Guidelines4/5

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

Provides explicit guidance: fetch current values with query_database before updating if a revert might be needed. Notes unsupported cases like plain troop updates and animations. However, does not directly compare to alternatives like create_database_entry or delete_database_entry.

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/DiegoLopez0208/RpgMakerMVUltimate-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server