Skip to main content
Glama
garuh143

RPG Maker MZ/MV MCP Server

by garuh143

search_items

Search RPG Maker MZ/MV game items by name or description to quickly locate specific assets in your project.

Instructions

Search items by name or description

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
searchTermYes

Implementation Reference

  • The implementation of the searchItems tool logic.
    export async function searchItems(projectPath: string, searchTerm: string): Promise<Item[]> {
      const items = await getItems(projectPath);
      const lowerSearchTerm = searchTerm.toLowerCase();
    
      return items.filter(item =>
        item && (
          item.name.toLowerCase().includes(lowerSearchTerm) ||
          item.description.toLowerCase().includes(lowerSearchTerm)
        )
      );
    }
  • The schema definition for the search_items tool registration.
    {
      name: 'search_items',
      description: 'Search items by name or description',
      inputSchema: {
        type: 'object',
        properties: {
          searchTerm: { type: 'string' },
        },
        required: ['searchTerm'],
      },
    },
  • src/index.ts:679-682 (registration)
    The registration/invocation handler in the main index file for the search_items tool.
      return await itemTools.updateItem(this.projectPath, args.itemId, args.updates);
    case 'search_items':
      return await itemTools.searchItems(this.projectPath, args.searchTerm);
Behavior2/5

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

No annotations provided, so description carries full burden. It fails to disclose matching behavior (partial vs exact, case sensitivity), return format, pagination limits, or what happens when no matches are found. No mention of whether this is a read-only operation (implied by 'search' but not stated).

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?

Single sentence with zero redundancy. However, extreme brevity contributes to under-specification; with no annotations or schema descriptions, the description could accommodate more detail without violating conciseness principles.

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 single-parameter search tool, it meets minimum viability by identifying the resource and search scope. However, lacks return value documentation (critical since no output schema exists) and behavioral constraints expected in a game development context (RPG Maker-like toolset).

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 has 0% description coverage. Description compensates partially by indicating searchTerm matches against both 'name' and 'description' fields, but lacks details on expected format, wildcards, or exact matching semantics.

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?

States specific action (Search) and resource (items) and searchable fields (name or description), which distinguishes it from sibling getters like get_items (likely by ID) and other search functions like search_actors or search_skills.

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?

Provides no guidance on when to use this versus get_items, update_item, or other item-related tools. No mention of prerequisites or when-not-to-use scenarios.

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