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

RPG Maker MZ Authoring MCP

by NixonMSilva
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Plugin command schemas

get_plugin_commands
Read-onlyIdempotent

Retrieves the commands and arguments declared in an RPG Maker MZ plugin's annotation header, returning inferred schemas so you can author plugin command blocks without inventing names.

Instructions

Commands and arguments declared in a plugin's annotation header (js/plugins/.js, read as text, never executed). Schemas are INFERRED from annotations; use them to author plugin_command blocks without inventing names.

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": {
      "pluginName": "<pluginName>"
    },
    "name": "get_plugin_commands"
  }
}

Input Schema

NameRequiredDescriptionDefault
pluginNameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description usefully adds that the file is 'read as text, never executed' and that schemas are 'INFERRED' — a meaningful reliability caveat about result trustworthiness. It does not describe return shape or failure behavior for an unknown plugin name.

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 tight sentences, zero filler, with the identity and safety constraint ('read as text, never executed') front-loaded before the usage hint. Every clause carries information.

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

Completeness4/5

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

For a single-parameter read tool with no output schema, the description conveys the source of truth, the inference caveat, and the intended consumer (plugin_command blocks). It is nearly sufficient, with only parameter format and error behavior left implicit.

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 0% for the single pluginName parameter, so the description carries the burden; it does imply pluginName is the plugin file stem via 'js/plugins/<name>.js', which is real added meaning. However, it never states expected format (bare name vs. path vs. .js suffix) or what happens when the plugin is missing.

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?

States a specific verb and resource: it returns commands and arguments declared in a plugin's annotation header, with the concrete file path pattern js/plugins/<name>.js. The domain ('plugin' commands vs. event commands) is inherent in the wording, though it never explicitly contrasts itself with siblings such as search_event_commands.

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?

Gives a clear downstream use case: 'use them to author plugin_command blocks without inventing names.' That tells an agent when this tool is the right one, but it names no alternative and gives no exclusion conditions, so it stops short of full routing guidance.

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