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

RPG Maker MZ Authoring MCP

by NixonMSilva
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List map events

list_map_events
Read-onlyIdempotent

Lists a map's events with IDs, names, coordinates, page counts and triggers, with paging and name filtering so you can locate the events to inspect or edit.

Instructions

Event IDs, names, coordinates, page counts and triggers on a map (paginated).

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

Input Schema

NameRequiredDescriptionDefault
limitNo
mapIdYes
offsetNo
nameContainsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered elsewhere. The only behavioral addition is '(paginated)', which merely restates the limit/offset parameters and gives no detail on default page size, maximum page size, 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.

Conciseness3/5

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

The definition is very short, which is good, but it is a sentence fragment with no subject or verb and leads with output fields rather than the operation. Brevity is achieved partly by omission rather than by tight editing.

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, enumerating returned fields is genuinely useful and arguably the description's main value. However, for a four-parameter paginated list tool with zero schema documentation, the definition does not say enough for an agent to call it correctly without guessing at parameter meanings.

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 four parameters, so the burden falls entirely on the description, yet mapId, nameContains, limit and offset are never explained. The listed items (coordinates, page counts, triggers) are return fields, not inputs, so they do not compensate for the gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource (map events on a map) and enumerates returned fields, but it is a noun-phrase fragment with no verb, so the action ('list') is only recoverable from the title. Nothing distinguishes it from siblings like list_common_events or list_map_events' own filtered variants.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no exclusion of alternatives (e.g., list_common_events, validate_map_events), and no mention of when the nameContains filter should be applied. The agent must infer all routing from other tools' names.

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