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

RPG Maker MV MCP Server

by Xerolo44
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Register plugin

add_plugin

Registers an existing js/plugins/.js file in the RPG Maker MV plugin list and fails if the file is missing; use create_plugin to create a new plugin.

Instructions

Register an existing js/plugins/.js file in the plugin list. Fails if the file does not exist (use create_plugin to make a new one).

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

Input Schema

NameRequiredDescriptionDefault
nameYes
statusNo
parametersNo
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.1

TDQS

A3.7/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 full disclosure burden. It usefully reveals the file-existence failure mode, but says nothing about whether registration is idempotent, whether it overwrites an existing entry with the same name, or what permissions/state effects registering has.

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 core action front-loaded and the routing hint following immediately.

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?

With no annotations, no output schema, and three undocumented parameters including a nested object, the description leaves too much for the agent to guess about what registering does with status and parameters. It is complete on purpose and error behavior but not on configuration or result.

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 0% across 4 parameters, and the description only implicitly explains 'name' via the file path. 'status', 'description', and especially the nested 'parameters' object (string-valued additionalProperties) are entirely opaque, which a low-coverage schema requires the description to compensate for.

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?

States a specific verb and resource ('Register an existing js/plugins/<name>.js file in the plugin list'), including the exact file-path shape the name parameter refers to. It explicitly contrasts with create_plugin, so an agent can distinguish the two without opening either schema.

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 precondition ('Fails if the file does not exist') and names the correct alternative for that case ('use create_plugin to make a new one'). It does not address where configure_plugin or remove_plugin fit in the lifecycle, so routing is clear for the main fork but not exhaustive.

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