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

RPG Maker MZ Authoring MCP

by NixonMSilva
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List switches

list_switches
Read-onlyIdempotent

Lists game switches with their names and reference counts across events, common events, and troops. Set onlyFree=true to find unnamed, unreferenced IDs for new logic without conflicts.

Instructions

Game switches with names and how many event/common-event/troop references use each. onlyFree=true lists unnamed, unreferenced IDs to use for new logic without conflicts.

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": "list_switches"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
onlyFreeNo
nameContainsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed world, so the safety profile is covered. The description adds real behavioral value by explaining what the returned records contain and what onlyFree changes. It says nothing about pagination behavior or result size, which matters given the limit/offset parameters and a 2000 maximum.

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

Conciseness4/5

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

Two dense sentences with no filler, and the core resource description is front-loaded ahead of the onlyFree hint. Phrasing is slightly telegraphic ('how many event/common-event/troop references use each'), but nothing is wasted.

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, the description usefully compensates by describing the shape of each returned entry, and the annotations cover safety. However, for a four-parameter tool at 0% schema coverage it leaves three parameters and the paging model unexplained, so it is only adequate rather than complete.

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%, so the description carries the burden for four parameters. It explains onlyFree well, but limit, offset and nameContains are given no meaning at all, leaving half the surface undocumented in both schema and prose.

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 concrete resource (game switches) and what each entry carries: name plus counts of event, common-event and troop references. That is specific enough to distinguish it from a bare 'list' sibling such as list_variables, though it never names an alternative explicitly.

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?

It gives one clear usage mode: set onlyFree=true to find unnamed, unreferenced IDs for new logic without conflicts. That is genuinely useful when-guidance, but there is no guidance on the default listing mode or on when to pick this over a related listing tool.

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