Skip to main content
Glama
Redseb

rpgmaker-mz-mcp

by Redseb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

batch_create

Create many RPG Maker MZ database records of one type in one call and one file write, for casts, loot tables, or skill lists instead of repeated single-record creates.

Instructions

Create many database records of one type in a single call and a single file write — the batch sibling of create_actor/create_item/create_weapon/create_armor/create_skill/create_enemy/create_state/create_class. Each entry in records takes the same fields its single create_* tool accepts (only name is required for most; omitted fields use the editor's defaults). Ids are allocated sequentially from the current max, so a record can reference a sibling created earlier in the same batch. Use this instead of N sequential create_* calls when authoring a cast, a loot table, or a skill list. Returns { type, count, created, warnings? } (classes are summarized like create_class; enemy battlerName misses and record fields the create_* tool doesn't accept are warnings, never blocked). Throws — writing nothing at all — if any record references a database id that does not exist, naming the offending records[i].

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesWhich database the records are appended to
dryRunNoPreview only: return a diff of what would change without writing to disk.
recordsYesThe records to create, each shaped like the matching create_* tool's arguments (e.g. for type "actor": { name, classId?, ... })

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations the description carries the whole burden and does so richly: sequential id allocation enabling intra-batch references, default filling for omitted fields, exact return shape, warnings that never block, and an atomic all-or-nothing throw naming records[i]. This is far beyond the schema.

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?

Front-loads the core purpose, then the alternative-routing, then return/error behavior. Slightly dense with the long sibling enumeration and parentheticals, but each clause conveys distinct information.

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?

No output schema exists, so the description usefully specifies the return object and error contract. For a 3-param batch-mutation tool with no annotations, nothing an agent needs to call it correctly is missing.

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 description coverage is already 100%, so baseline is 3, but the description adds real meaning: `records` entries take the create_* tool's fields with only `name` required for most types, and ids are allocated sequentially so earlier entries can be referenced later. The dryRun preview semantics are restated but consistent with the schema.

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?

Specific verb+resource ('Create many database records of one type in a single call') and explicitly positions itself as the batch sibling of the eight single create_* tools. An agent can distinguish it from any sibling without opening a schema.

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

Usage Guidelines5/5

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

Names the alternative ('Use this instead of N sequential create_* calls') and gives concrete triggering scenarios (authoring a cast, a loot table, a skill list). When-to-use is fully explicit.

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