Skip to main content
Glama
Redseb
by Redseb

create_map_event

Create a new event on a map. Merge only fields that differ onto a blank page, with validation and dry-run preview.

Instructions

Create a new event on a map. Each page is merged onto a blank "New Event" page (trigger 0 action-button, priority 0 below characters, no graphic, empty command list, standing move type), so you only supply the fields that differ — pass e.g. { image: { characterName: 'Actor1', characterIndex: 0 }, trigger: 3, list: [...] } and the rest is filled in. Nested image/conditions deep-merge; an omitted list becomes a valid empty (code-0-terminated) list. Omit pages entirely for a bare one-page event. For the common "talking NPC" case prefer create_npc. An action-button page meant to fire from facing (doors, entrances, signs) needs priorityType: 1 — with the default 0 (below) it only fires when stood on, so on an impassable tile it can never trigger (this is refused, not written; pass force: true to override). A structurally invalid command list is refused the same way. Page fields: image { characterName, characterIndex, direction (2 down/4 left/6 right/8 up), pattern, tileId }, trigger (0 action-button/1 player-touch/2 event-touch/3 autorun/4 parallel), priorityType (0 below/1 same/2 above), moveType (0 fixed/1 random/2 approach/3 custom), conditions, list.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xYesX tile position
yYesY tile position
nameYesEvent name
noteNoEvent note field
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.
mapIdYesThe ID of the map
pagesNoEvent pages; each is merged onto a blank page so you can pass only the differing fields. Omit for one blank page.
dryRunNoPreview only: return a diff of what would change without writing to disk.
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 excels. It exposes default page values, deep-merge behavior, empty-list handling, validation refusals, and the facing-trigger pitfall, all of which are critical behavioral specifics 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.

Conciseness5/5

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

Every sentence contributes unique operational detail; the text is front-loaded with purpose, uses an inline example, and ends with a structured field list. For a tool with 8 parameters and complex merge semantics, the length is justified and there is no waste.

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?

Given the absence of annotations and output schema, this description supplies complete context. It covers defaults, enums, merge rules, validation behavior, page attributes, and sibling-tool alignment, enabling an agent to invoke the tool correctly without external documentation.

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?

The input schema only gives generic descriptions like 'Event pages', but the description adds concrete field formats including image parameters, trigger/priorityType/moveType enums, conditions, and list termination. This goes far beyond the schema and is essential for correct invocation.

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?

Description opens with 'Create a new event on a map' and immediately defines the tool's scope via the merge model. It also distinguishes from the sibling create_npc by explicitly recommending that tool for talking NPCs, so the agent can tell them apart.

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?

Provides direct when-to-use guidance: 'For the common "talking NPC" case prefer create_npc' and explains when priorityType:1 is required for action-button pages. It also covers validation refusal and the force override, so the agent knows the failure modes and how to handle them.

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/Redseb/rpgmaker-mz-mcp'

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