Skip to main content
Glama
garuh143

RPG Maker MZ/MV MCP Server

by garuh143

search_map_events

Find events on a specific RPG Maker map by searching for their names to locate and manage game interactions and triggers.

Instructions

Search events on a map by name

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mapIdYes
searchTermYes

Implementation Reference

  • The handler function for search_map_events which fetches map events and filters them by a search term.
    export async function searchMapEvents(
      projectPath: string,
      mapId: number,
      searchTerm: string
    ): Promise<MapEvent[]> {
      const events = await getMapEvents(projectPath, mapId);
      const lowerSearchTerm = searchTerm.toLowerCase();
    
      return events.filter(event =>
        event && event.name.toLowerCase().includes(lowerSearchTerm)
      ) as MapEvent[];
    }
Behavior2/5

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

With no annotations provided, the description fails to disclose critical behavioral traits such as whether the search supports partial matching, case sensitivity, or what fields are searched. It also omits what the tool returns.

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?

The description consists of a single efficient sentence with no redundant words, earning high marks for brevity. However, given the complete lack of schema documentation, this extreme conciseness results in under-specification.

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?

Considering the tool has two undocumented parameters (0% schema coverage), no annotations, and no output schema, the description fails to provide sufficient context regarding parameter usage or return behavior, leaving significant gaps in the agent's understanding.

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?

The schema has 0% description coverage. While the description implies that mapId refers to the map and searchTerm refers to the event name, it does not explicitly document parameter semantics, valid formats, or whether the search term requires exact matches.

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 uses a specific verb 'Search' and identifies the resource as 'events on a map', specifying the search criterion 'by name'. It implicitly distinguishes from create_map_event and update_map_event, though it could better clarify when to use this versus get_map_events.

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?

The description provides no explicit guidance on when to prefer this tool over get_map_events or get_map_event, nor does it mention prerequisites such as requiring a valid mapId or the format of the searchTerm.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/garuh143/RPG-MakerMV-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server