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

RPG Maker MV MCP Server

by Xerolo44
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Event command reference

event_command_reference

Access a reference table of RPG Maker MV event command codes and parameters to verify commands and arguments before writing or editing event lists.

Instructions

Reference table of RPG Maker MV event command codes and their parameters. Consult this before writing or editing event command lists.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.1

TDQS

A3.8/5.0
Behavior3/5

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

No annotations exist, so the description carries the burden. 'Reference table' implies a safe read operation, but the description never states that it is read-only, what shape the reference data takes, how complete the code coverage is, or whether it is version-scoped. Adequate but thin for a tool with zero structured behavior metadata.

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?

Two sentences, zero waste, with the identity of the resource front-loaded and the actionable instruction second. Exactly the right size for a zero-param lookup.

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

Completeness3/5

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

With no output schema and no annotations, the description is the only source of information about what the agent gets back. It says 'reference table' but not the return shape, coverage, or whether it includes examples, which leaves a real gap for a tool whose entire value is its output.

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 tool takes zero parameters, which is the baseline-4 case; there is nothing for the description to disambiguate. No misleading parameter hints are present.

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 states a specific resource ('RPG Maker MV event command codes and their parameters') and frames it as a reference/lookup table, which is clearly distinct from mutation siblings like add_event_command or update_event. It stops short of naming a specific sibling to contrast with, keeping it at a solid 4 rather than 5.

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?

Explicitly says when to use it: 'Consult this before writing or editing event command lists,' which directly points the agent at the pre-write phase and implicitly steers away from the mutating siblings. No explicit exclusions or named alternatives are given, so 4 is right.

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