Skip to main content
Glama
garuh143

RPG Maker MZ/MV MCP Server

by garuh143

search_actors

Find RPG Maker actors by name or nickname to manage game character data in MZ/MV projects.

Instructions

Search actors by name or nickname

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
searchTermYesThe search term to find actors

Implementation Reference

  • The handler function that performs the actor search logic by filtering based on name or nickname.
    export async function searchActors(projectPath: string, searchTerm: string): Promise<Actor[]> {
      const actors = await getActors(projectPath);
      const lowerSearchTerm = searchTerm.toLowerCase();
    
      return actors.filter(actor =>
        actor && (
          actor.name.toLowerCase().includes(lowerSearchTerm) ||
          actor.nickname.toLowerCase().includes(lowerSearchTerm)
        )
      );
    }
  • src/index.ts:164-176 (registration)
    The tool definition for 'search_actors' registered in the MCP server.
      name: 'search_actors',
      description: 'Search actors by name or nickname',
      inputSchema: {
        type: 'object',
        properties: {
          searchTerm: {
            type: 'string',
            description: 'The search term to find actors',
          },
        },
        required: ['searchTerm'],
      },
    },
  • src/index.ts:666-667 (registration)
    The tool dispatch logic in the MCP server that routes 'search_actors' to the appropriate handler.
    case 'search_actors':
      return await actorTools.searchActors(this.projectPath, args.searchTerm);
Behavior2/5

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

No annotations are provided, so the description must carry full behavioral disclosure burden. It only mentions that the search covers 'name or nickname' fields, but fails to disclose matching behavior (partial vs exact, case sensitivity), result limits, or return format. For a read operation with no safety annotations, this is insufficient behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

The description is a single six-word sentence with zero waste. It is immediately front-loaded with the action (Search) and target (actors). Every word earns its place in conveying the core purpose.

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 with 100% schema coverage and no output schema, the description provides the essential functional context (what fields are searched). However, it lacks guidance on when to use this versus get_actor or get_actors, leaving a gap in contextual completeness for the agent's decision-making.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema coverage, the baseline is 3. The description adds valuable semantic context by specifying that the searchTerm applies to 'name or nickname' fields, helping the agent understand what data the parameter searches against beyond the generic schema description.

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?

Uses specific verb (Search) + resource (actors) + scope (by name or nickname). The inclusion of 'nickname' distinguishes this from a strict ID-based lookup (get_actor) and clarifies the searchable fields, though it does not explicitly contrast with get_actors or sibling search tools.

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 tool versus alternatives like get_actor (likely ID-based) or get_actors (likely list all). No prerequisites, exclusions, or explicit alternative recommendations are mentioned.

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