RPG Maker MZ Authoring MCP

Overview Schema Source Related Servers Discussions Admin

List common events

list_common_events

Read-onlyIdempotent

Retrieve paginated common event IDs, names, and trigger types from an RPG Maker MZ project, with optional name filtering and offset/limit controls for browsing events.

Instructions

Common event IDs, names and triggers (paginated).

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_common_events"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`offset`	No
`nameContains`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 14, 2026

TDQS

C2.4/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so safety behavior is fully covered by structured data. The description adds only the pagination note, and doesn't disclose default page size, ordering, or that limit accepts a negative minimum despite a 500 maximum.

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?

It's a single short fragment with zero waste and the resource is front-loaded, but the terseness is under-specification rather than effective conciseness. It is not a complete sentence and communicates less than a one-line description could.

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

Completeness2/5

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

Three undocumented parameters, no output schema, and a bare eight-word description leave the agent without enough to filter or paginate confidently. For a list tool with a filter parameter, the definition should say what nameContains matches and how paging behaves.

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% for all three parameters, so the description carries the full burden and mostly fails. 'Paginated' loosely implies limit/offset, but nameContains (the only filter) is never mentioned, and the unusual negative minimum on limit is unexplained.

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 fragment names the resource (common events) and what it returns (IDs, names, triggers), which is enough to know it's a read/list operation only because the tool name contains 'list'. There is no verb in the description and no differentiation from siblings like list_map_events or list_event_templates, which the agent must infer from names alone.

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 guidance on when to call this versus list_map_events, list_event_templates, or get_common_event. The only hint is '(paginated)', which does not tell the agent what condition would select this tool over the alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server