Skip to main content
Glama
garuh143

RPG Maker MZ/MV MCP Server

by garuh143

get_items

Retrieve all item data from RPG Maker MZ/MV projects to manage game assets, enabling users to access and organize items for game development.

Instructions

Get all items from the project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The implementation of the getItems tool, which reads the Items.json file from the specified project path.
    export async function getItems(projectPath: string): Promise<Item[]> {
      const itemsPath = getDataPath(projectPath, 'Items.json');
      return await readJsonFile<Item[]>(itemsPath);
    }
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 but offers minimal behavioral context. While 'Get' implies read-only, there is no confirmation of safety, no mention of idempotency, error conditions (e.g., empty project), or pagination behavior for potentially large datasets.

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

Conciseness4/5

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

The single sentence is appropriately front-loaded and efficient with no wasted words. However, it is under-informative rather than optimally concise, lacking necessary context for the domain.

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?

Given the absence of an output schema and annotations, and the moderate complexity suggested by numerous siblings, the description is minimally adequate but has clear gaps. It fails to define the 'item' entity type or describe the return structure.

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?

The tool has zero parameters, which per evaluation rules establishes a baseline of 4. The description implies no filtering is needed (consistent with 'all items'), matching the empty input schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the basic action (get) and resource (items) but lacks domain-specific clarity. Given siblings like get_weapons, get_armors, and search_items, it fails to specify that 'items' refers to a specific entity category (e.g., consumable items distinct from equipment) or distinguish its 'get all' scope from the filtering behavior of search_items.

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_items, nor any prerequisites or conditions. An agent cannot determine from the description alone whether to retrieve all items with this tool or search with the sibling.

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