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

RPG Maker MZ Authoring MCP

by NixonMSilva
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Find references

find_references
Read-onlyIdempotent

Find every known reference to a switch, variable, database record, common event, map, or map event, including low-confidence script matches.

Instructions

Reverse lookup: every known reference to a switch, variable, database record, common event, map, or map event (refKind "event" needs mapId). Includes low-confidence matches inferred from script text.

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": {
      "refKind": "<refKind>",
      "id": "<id>"
    },
    "name": "find_references"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
mapIdNo
eventIdNoFor self_switch: the owning event
refKindYes

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 readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds one genuinely useful behavioral fact beyond them: results include low-confidence matches inferred from script text, so the agent knows output is heuristic and not purely structural. It still says nothing about result shape or ordering.

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 tight sentences with the core operation front-loaded and the caveats parked in a parenthetical and a trailing clause. Nothing is redundant, though the density makes it read more like a spec fragment than prose.

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 four-parameter lookup with no output schema and low schema coverage, the definition covers the input side reasonably but never hints at what a reference entry looks like. An agent knows how to call it but not what it will get back.

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 only 25%, so the description carries real weight here: it enumerates the valid refKind values (which have no enum in the schema) and states that refKind "event" requires mapId. The id and mapId parameters remain unexplained beyond their names, so compensation is partial rather than complete.

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 opens with a specific framing ("Reverse lookup") and enumerates exactly which resource types can be looked up (switch, variable, database record, common event, map, map event). An agent can tell what it returns, though it never names a sibling such as database_find_references to disambiguate the two lookups.

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 implied by "every known reference to X" — you call it when you need to know what depends on an object. The parenthetical "refKind \"event\" needs mapId" is a genuine precondition worth having, but there is no explicit when-not guidance or pointer to alternatives.

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