Skip to main content
Glama

create_state

Create a new status effect (poison, sleep, buff, etc.) for RPG Maker, configuring behavior like removal timing, restrictions, and traits.

Instructions

Create a new state (poison, sleep, confusion, buff, etc.).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesState name
iconIndexNoIcon index
restrictionNoRestriction: 0=none, 1=attack enemy, 2=attack ally, 3=attack anyone, 4=cannot move
priorityNoState priority (default 50)
removeAtBattleEndNoRemove when battle ends (default false)
removeByDamageNoChance to remove when damaged (default false)
autoRemovalTimingNoAuto remove: 0=none, 1=action end, 2=turn end
minTurnsNoMinimum turns (default 1)
maxTurnsNoMaximum turns (default 5)
traitsNoTrait objects {code, dataId, value}
message1NoMessage when applied
message2NoMessage when remaining
message3NoMessage when removed
message4NoMessage on failure
noteNoNote field
removeByRestrictionNoRemove by restriction (default false)
stepsToRemoveNoSteps to remove (default 100)
Behavior1/5

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

No annotations provided. The description does not disclose any behavioral traits such as side effects, permission requirements, or if the state is immediately available after creation. It fails to compensate for the lack of annotations.

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?

One sentence, front-loaded with examples. Extremely concise with no unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 17 parameters and no output schema or annotations, the description is far too brief. It does not explain how traits work, how parameters interact, or what the tool returns. Incomplete 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.

Parameters3/5

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

Schema coverage is 100% so the schema documents all parameters. The description adds no additional meaning beyond what is already in the schema. Baseline 3 is appropriate.

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 verb 'create' and resource 'state', and provides examples like poison, sleep, confusion, buff. This distinguishes it from sibling tools like update_state (update existing) and create_state_skill (skill that applies a state).

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives such as create_state_skill. No mention of when not to use or prerequisites.

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/DiegoLopez0208/RpgMakerMVUltimate-MCP'

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