Skip to main content
Glama
Redseb
by Redseb

reset_table

Wipe a database table except chosen IDs to start authoring your own RPG Maker MZ database. Preview changes with dryRun, keep core records, avoid dangling references.

Instructions

Clear a whole database table (actor, class, skill, item, weapon, armor, enemy, troop, state, or common_event) except the ids in keep — e.g. reset_table('skill', { keep: [1, 2] }) wipes the RTP skills but keeps Attack/Guard, the usual first step before authoring your own database with batch_create. Kept records stay at their own id; the rest become null and trailing empty slots are trimmed (the table is [null] when nothing is kept). Like delete_record it REFUSES, writing nothing, when the removal would leave references dangling (map events giving removed items, troops of removed enemies, …) unless force: true; use dryRun: true first to see what disappears and what would break. Returns { type, kept[], removedCount, removed[], referenceCount, references[], coverage } (lists are capped at 100).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keepNoIds to keep (each must exist); omitted = remove every record
typeYesWhich database table: actor, class, skill, item, weapon, armor, enemy, troop, state, or common_event
forceNoWrite even if validation finds structural problems (wrong parameter count, unterminated command list). Off by default: such a write is refused and nothing is written. Advisory warnings never block regardless.
dryRunNoPreview only: return a diff of what would change without writing to disk.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.4.0

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so thoroughly: it discloses destructive clearing, REFUSAL on dangling references unless force: true, dryRun preview semantics, id preservation, null/trimming behavior, and return shape with a 100-item cap.

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 long but front-loads the action, effect, example, safety behavior, and return shape with no empty filler. The enumerated table types duplicate the schema enum and add some bulk, keeping it from a perfect score.

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?

For a complex destructive tool with no annotations and no output schema, the description supplies the missing return shape, refusal conditions, dryRun behavior, and trimming rules. An agent has everything needed to invoke it safely and interpret the result.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description adds value beyond the schema by demonstrating the keep array in an example and explaining force vs. dryRun behavior in context. The type enum is already in the schema, so no extra credit there.

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?

States a specific verb ('Clear'), resource ('whole database table'), and enumerates the table types. The example reset_table('skill', { keep: [1, 2] }) concretely shows the tool's effect, letting an agent distinguish it from single-record tools like delete_record.

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?

Gives clear usage context: 'the usual first step before authoring your own database with batch_create' and advises 'use dryRun: true first.' It also notes refusal behavior like delete_record, but does not explicitly state when to prefer this over delete_record or other alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools