Skip to main content
Glama
garuh143

RPG Maker MZ/MV MCP Server

by garuh143

get_armors

Retrieve all armor data from RPG Maker MZ/MV projects to access game equipment details for development and management tasks.

Instructions

Get all armors from the project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that retrieves armor data from Armors.json.
    export async function getArmors(projectPath: string): Promise<Armor[]> {
      const armorsPath = getDataPath(projectPath, 'Armors.json');
      return await readJsonFile<Armor[]>(armorsPath);
    }
Behavior3/5

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

No annotations provided, so description carries full burden. It correctly establishes the broad scope ('all armors') implying no filtering capability, but fails to disclose return format, pagination behavior, or performance implications of retrieving unbounded collections.

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?

Single sentence with no redundancy. Every word earns its place by stating operation, resource, and scope. Front-loaded and appropriately sized for tool complexity.

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?

Minimal but viable for a zero-parameter read operation. Lacks return value documentation (no output schema exists to compensate), and does not clarify armor categorization relative to items/weapons siblings. Adequate for invocation but leaves operational context gaps.

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?

Zero parameters present; description baseline is 4. The phrase 'Get all' appropriately reinforces the schema's lack of filter parameters, confirming no user input is expected for scoping.

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?

Clear verb (Get), resource (armors), and scope (all, from the project). However, lacks explicit differentiation from siblings like get_items or get_weapons which may represent overlapping categories in game data.

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?

No guidance provided on when to use this versus search/filter alternatives (e.g., if a user wants specific armors) or prerequisites. The description states what it does but not when to prefer it over sibling tools.

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