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

RPG Maker MZ Authoring MCP

by NixonMSilva
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Select project

select_project
Read-onlyIdempotent

Switch the active RPG Maker MZ project by index, folder name, or path so subsequent authoring actions target the intended project.

Instructions

Switch the active project to one of the configured projects (by index, folder name or path).

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

Input Schema

NameRequiredDescriptionDefault
projectYesIndex, folder name or path of a configured project

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the agent knows repeating the call is safe and no project data is mutated. The description adds the useful constraint that only configured projects are eligible, but says nothing about failure behavior for an unknown name, path resolution rules, or whether the selection persists across calls.

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?

A single front-loaded sentence with no boilerplate or redundancy; the accepted identifier forms are packed into a compact parenthetical. Nothing could be removed without losing information.

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?

The tool is simple, needs no output schema, and its annotations carry the safety profile, so the description is nearly sufficient. The one real gap for a single-argument selection tool is the ambiguous "index" (zero- versus one-based) and what error surfaces for an unknown path.

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% and the description's parenthetical ("by index, folder name or path") merely repeats the schema's parameter description verbatim. With one fully documented parameter, the baseline of 3 applies; no additional meaning such as index base (0 or 1) or path format is provided.

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 concrete verb and object ("Switch the active project") plus the population of valid targets ("one of the configured projects"), so the agent knows exactly what changes. It does not contrast itself with the closest sibling, get_project_info, which inspects rather than switches.

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

Usage Guidelines3/5

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

Usage is only implied: the agent can infer this is the tool to call when work should target a different project. There is no explicit when-to-use/when-not framing, no note about needing to run get_project_info or validate_project_references first, and no statement of what happens to the previously active project.

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