Skip to main content
Glama
Redseb
by Redseb

set_event_page

Update an event page's appearance and behavior in a single call without rebuilding it or altering its command list, with validation that prevents unreachable page changes.

Instructions

Update an existing event page's graphic and behavior in one call, without rebuilding the whole page or touching its command list: sprite (characterName/characterIndex/direction/pattern or a tileId), trigger, priority, movement (type/speed/frequency/route), and the through/walkAnime/stepAnime/directionFix flags. Graphic fields merge onto the current image; warns (never blocks) on an unknown characterName. Refuses the write if the change would leave the event unreachable (an action-button page with priority below on an impassable tile) — pass force: true to override.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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
dryRunNoPreview only: return a diff of what would change without writing to disk.
indentNo(unused; page-level tool)
tileIdNoUse a tile as the graphic instead of a sprite (0 = none)
eventIdYesThe ID of the event
patternNoSprite animation frame 0–2 (1 = idle)
throughNoLet the player/others pass through the event
triggerNoWhat starts the page
moveTypeNoAutonomous movement (custom uses moveRoute)
priorityNoStacking vs. the player: below/same/above characters (same = solid)
directionNoFacing direction of the sprite
moveRouteNoAutonomous move route (from create_move_route); pairs with moveType "custom"
moveSpeedNoMovement speed 1–6 (4 = normal)
pageIndexYesZero-based page index
stepAnimeNoAnimate in place while stopped
walkAnimeNoAnimate the walk cycle while moving
directionFixNoLock the facing direction
characterNameNoSprite sheet basename (from list_assets("characters")); "" = no sprite
moveFrequencyNoMovement frequency 1–5 (3 = normal)
characterIndexNoSprite index 0–7 in the sheet
Behavior5/5

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

With no annotations provided, the description carries full responsibility for disclosing behavior. It does this thoroughly: 'Graphic fields merge onto the current image' reveals merging behavior, 'warns (never blocks) on an unknown characterName' clarifies warning semantics, and 'Refuses the write... pass force: true to override' explains validation and override behavior. This goes well beyond basic expectations.

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?

The description is dense but efficient, with every sentence adding value. It front-loads the primary action, lists the parameter groups, and then explains key behavioral nuances. No filler or repetition; it earns its length given the tool's complexity.

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?

Despite having 21 parameters and no output schema, the description covers the essential behaviors: merging, warning, refusal with force override, and preservation of the command list. The schema handles parameter-level details, while the description addresses high-level context and edge cases. This is complete for a tool of this complexity.

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?

The input schema already provides 100% parameter descriptions, meeting the baseline. The tool description adds meaningful value by grouping related parameters (e.g., 'sprite (characterName/characterIndex/direction/pattern or a tileId)', 'movement (type/speed/frequency/route)') and clarifying semantics like 'Graphic fields merge' and the effect of 'force: true'. This is above baseline but not exhaustive for all 21 parameters.

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 the tool's function: 'Update an existing event page's graphic and behavior in one call'. It specifies the resource (existing event page), the action (update), and the scope (graphic and behavior). It also differentiates from siblings by explicitly noting 'without rebuilding the whole page or touching its command list', distinguishing it from broader event-map tools.

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?

The description provides clear context for when to use the tool: for targeted page graphic/behavior updates while preserving the command list. However, it does not explicitly name alternative tools or provide when-not-to-use exclusions. The context is strong but lacks explicit alternative reference, so a 4 is appropriate.

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