Skip to main content
Glama
garuh143

RPG Maker MZ/MV MCP Server

by garuh143

get_weapons

Retrieve all weapon data from RPG Maker MZ/MV projects to manage game assets and integrate with MCP-compatible clients for game development.

Instructions

Get all weapons from the project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that retrieves all weapons by reading Weapons.json from the project path.
    export async function getWeapons(projectPath: string): Promise<Weapon[]> {
      const weaponsPath = getDataPath(projectPath, 'Weapons.json');
      return await readJsonFile<Weapon[]>(weaponsPath);
    }
  • src/index.ts:188-194 (registration)
    The MCP tool registration for 'get_weapons'.
      name: 'get_weapons',
      description: 'Get all weapons from the project',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • The tool invocation mapping that calls the getWeapons handler.
    case 'get_weapons':
      return await itemTools.getWeapons(this.projectPath);
Behavior2/5

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

No annotations provided, so description carries full burden. While 'Get' implies read-only behavior, the description fails to disclose return format, pagination behavior, or potential performance implications of retrieving 'all' weapons.

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 of six words with no redundant information. Purpose is front-loaded and immediately clear despite brevity.

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?

Adequate for a simple parameter-less getter, but lacks description of return structure despite absence of output schema. Should indicate what weapon properties are returned (e.g., name, damage, icon).

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?

Input schema contains zero parameters. Per scoring rules, zero-parameter tools receive a baseline score of 4 as there are no parameters requiring semantic clarification.

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 verb 'Get' and resource 'weapons', distinguishing from siblings like get_items, get_armors, and get_skills. 'From the project' provides context but remains slightly vague about the domain (game development).

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_items (which may return weapons as a subset) or search functions. No prerequisites or exclusion criteria 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