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

RPG Maker MZ Authoring MCP

by NixonMSilva
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List variables

list_variables
Read-onlyIdempotent

Lists game variables with names and how many event, common-event and troop references use each; set onlyFree to true to find unnamed, unreferenced IDs for conflict-free new logic.

Instructions

Game variables 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_variables"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
onlyFreeNo
nameContainsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/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 scope, so safety is covered. The description adds genuine behavioral content by describing the returned shape (names plus reference counts) and the semantic meaning of free slots. It says nothing about pagination defaults or result ordering, which matters for a paged list.

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 compact sentences with the return shape front-loaded and the mode flag explained second. The first sentence is a noun fragment rather than a full clause, which is slightly terse but costs no clarity.

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?

For a read-only list tool with no output schema, the description does tell the agent what fields come back, which is the main need. Gaps remain around pagination defaults and the nameContains filter, both of which an agent must guess when composing a call.

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%, so the description carries the burden; it explains onlyFree clearly, which is the non-obvious parameter. limit, offset, and nameContains are left entirely undocumented, though their names are conventional enough that an agent can infer filtering and paging.

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?

Names the specific resource (game variables) and states exactly what each entry carries: the name plus counts of event/common-event/troop references. The sibling list_switches is a parallel concept, and the reference-count framing makes this tool's output distinguishable, though the description never explicitly says it is a listing operation beyond the title.

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?

Gives one explicit conditional: onlyFree=true for picking unnamed, unreferenced IDs when creating new logic. The default mode's use case (auditing existing variable usage) is only implied, and there is no guidance on when to prefer this over the switch-listing counterpart.

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