search_enemies
Search enemies by name in your RPG Maker project, with case-insensitive matching for flexible retrieval.
Instructions
Search enemies by name (case-insensitive).
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Search term |
Search enemies by name in your RPG Maker project, with case-insensitive matching for flexible retrieval.
Search enemies by name (case-insensitive).
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Search term |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses case-insensitivity as a behavioral trait, but with no annotations, it misses other important aspects like return format, pagination, or read-only nature.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single sentence with no wasted words, front-loading the key information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple search tool with one parameter and no output schema, the description is adequate but fails to mention what the tool returns (e.g., list of matching enemies), leaving some uncertainty for the agent.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description adds specific meaning to the 'query' parameter by stating it searches by name and is case-insensitive, which goes beyond the schema's generic 'Search term' description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'search', the resource 'enemies', and the method 'by name (case-insensitive)'. It distinguishes from sibling search tools by specifying the resource type.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage for finding enemies by name but provides no explicit guidance on when to use this tool versus other search tools like search_actors or search_items.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/DiegoLopez0208/RpgMakerMVUltimate-MCP'
If you have feedback or need assistance with the MCP directory API, please join our Discord server