Skip to main content
Glama
garuh143

RPG Maker MZ/MV MCP Server

by garuh143

search_skills

Find RPG Maker MZ/MV skills by searching through names and descriptions to locate specific game abilities.

Instructions

Search skills by name or description

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
searchTermYesSearch term

Implementation Reference

  • The implementation of the search_skills tool handler, which filters skills by name or description.
    export async function searchSkills(projectPath: string, searchTerm: string): Promise<Skill[]> {
      const skills = await getSkills(projectPath);
      const lowerSearchTerm = searchTerm.toLowerCase();
    
      return skills.filter(skill =>
        skill && (
          skill.name.toLowerCase().includes(lowerSearchTerm) ||
          skill.description.toLowerCase().includes(lowerSearchTerm)
        )
      );
    }
Behavior2/5

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

With no annotations provided, the description carries the full disclosure burden. It indicates the tool searches across both name and description fields, but omits critical behavioral details: matching logic (substring vs. exact), case sensitivity, result limits, return format, and whether results include full objects or just IDs.

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 optimally concise at four words, front-loaded with the action verb 'Search', and contains no redundancy. Every word contributes essential information about the tool's function.

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 without output schema, the description covers the basic purpose but leaves gaps. It should clarify the relationship with get_skills and indicate what the search returns (IDs, objects, or references) given the lack of output schema documentation.

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?

While the schema has 100% coverage with 'Search term', the description adds valuable semantic context that the term is matched against both name AND description fields. This clarifies the search scope beyond what the parameter description alone provides.

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 clearly states the verb (Search), resource (skills), and scope (by name or description). It implicitly distinguishes from sibling get_skills by specifying the text-based search mechanism, though it doesn't explicitly name the alternative tool.

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 guidance on when to use this tool versus alternatives like get_skills (likely for ID-based retrieval) or search_actors/search_items. No prerequisites, exclusions, or decision criteria 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