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

RPG Maker MZ Authoring MCP

by NixonMSilva
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get common event

get_common_event
Read-onlyIdempotent

Retrieve a common event's trigger, condition switch, and logic description; request detailed output to include the event's IR for inspection and authoring.

Instructions

A common event's trigger, condition switch and logic description (detailed=true also returns the Event IR).

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": {
      "commonEventId": "<commonEventId>"
    },
    "name": "get_common_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
detailedNo
commonEventIdYes

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 readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds one genuinely useful behavioral fact beyond them: that detailed=true expands the response to include Event IR. Nothing is said about response size, cost, or behavior for missing IDs.

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?

A single front-loaded sentence with the expansion flag tucked into a parenthetical, so the primary payload is read first. Nothing is wasted, though the sentence fragment phrasing lacks an explicit verb.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With two parameters, no output schema, and annotations covering safety, the description covers the main thing an agent cannot infer from structured fields: the detailed flag's effect on the payload. The unexplained commonEventId and absent sibling routing are the only real gaps.

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 description coverage is 0%, so the description must compensate, and it only partly does: it explains what detailed=true yields but says nothing about commonEventId (its range, whether it is a database/common-event list identifier). Partial compensation keeps this at the minimum-viable level.

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 names the specific resource (a common event) and enumerates exactly what is returned: trigger, condition switch, and logic description. That is clear enough to distinguish it from list_common_events, though it does not explicitly contrast with getter siblings like get_event_logic or get_event_ir_reference.

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 and no exclusions. The parenthetical hints that detailed=true is the path to Event IR, but it never states when an agent should prefer this tool over the sibling IR/logic getters.

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