Skip to main content
Glama
Redseb
by Redseb

create_state

Create a status condition (like Poison or Sleep) in RPG Maker MZ's States.json. Only a name is required; the tool assigns the next unused state ID automatically.

Instructions

Create a new state (status condition like Poison/Sleep) in data/States.json. Only name is required; omitted fields use the editor's new-state defaults (no restriction, priority 50, no auto-removal, 1-turn duration). Allocates and returns the next unused state id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesState name shown in the database and battle messages
noteNoNote field
dryRunNoPreview only: return a diff of what would change without writing to disk.
motionNoSV-actor motion (0 normal, 2 sleep, 3 dead, …)
traitsNoTrait objects { code, dataId, value }
overlayNoOverlay animation index (0 = none)
maxTurnsNoMaximum duration in turns when auto-removed
message1NoMessage when an actor gains the state
message2NoMessage when an enemy gains the state
message3NoMessage when the state persists
message4NoMessage when the state is removed
minTurnsNoMinimum duration in turns when auto-removed
priorityNoIcon-slot display priority 0-100 (default 50)
iconIndexNoIcon shown on the battler/status (0 = none)
messageTypeNoEngine's message routing form
restrictionNoBehavior restriction: 0 none, 1 attack enemy, 2 attack anyone, 3 attack ally, 4 cannot move
stepsToRemoveNoSteps to walk off the state when removeByWalking
chanceByDamageNoChance (%) of removal per damage instance when removeByDamage
removeByDamageNoRemove when the battler takes damage
releaseByDamageNoWhether damage can release the state
removeByWalkingNoRemove after walking a number of steps
autoRemovalTimingNoAuto-removal timing: 0 none, 1 at action end, 2 at turn end
removeAtBattleEndNoRemove automatically when the battle ends
removeByRestrictionNoRemove when the battler's restriction changes
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 performs excellently. It discloses that omitted fields use editor defaults, specifies those defaults (no restriction, priority 50, no auto-removal, 1-turn duration), and states that it allocates and returns the next unused state id. This is highly transparent about behavior and side effects.

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 three brief sentences, each with a distinct purpose: what the tool does, default behavior, and return value. No redundancy or filler.

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 the tool's complexity (24 parameters, no output schema), the description covers essential contextual aspects: creation target, required fields, defaults, and return ID. This is sufficient for an agent to use the tool correctly.

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?

All 24 parameters have schema descriptions, giving 100% coverage. The description adds value by explaining the defaults for omitted fields, which the schema does not convey, thus supplementing the schema meaningfully.

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

Purpose4/5

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

The description clearly states the tool creates a new state (status condition) in data/States.json, with a specific verb and resource. However, it does not explicitly contrast with sibling tools like update_state, so it does not fully distinguish from alternatives.

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 explains that only name is required and omitted fields use editor defaults, providing clear usage context. It does not mention when to use this versus update_state or other alternatives, but the creation purpose is straightforward and no exclusions are stated.

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