Skip to main content
Glama
Sign In
RPG Maker MZ MCP Server

RPG Maker MZ MCP Server

by devmagary
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

update_state

Update properties of an existing state in RPG Maker MZ, such as name, icon, or turn duration.

Instructions

Update an existing state's properties

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "update_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesState ID to update
nameNo
iconIndexNo
minTurnsNo
maxTurnsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, the description should disclose behavioral traits. It only says 'Update' implying mutation, but fails to mention if the operation is idempotent, requires permissions, or error handling for non-existent states.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The description is a single concise sentence with no wasted words. However, it may be too brief to convey essential information, balancing conciseness with clarity.

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

Completeness2/5

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

Given no output schema and no annotations, the description is too incomplete. It does not explain return values, error conditions, or the effect of each parameter, leaving significant gaps for the agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

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

Schema description coverage is only 20% (id has a description). The description does not add meaning to the other parameters (name, iconIndex, minTurns, maxTurns) beyond what the schema provides, which is minimal.

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 that this tool updates an existing state's properties. It distinguishes from get_states (read) and create_state (create) tools. However, it does not specify which properties can be updated beyond the schema.

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 is provided on when to use this tool versus alternatives like create_state or other update tools. There is no mention of prerequisites, context, or trade-offs.

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