Skip to main content
Glama
garuh143

RPG Maker MZ/MV MCP Server

by garuh143

get_actors

Retrieve all actor data from your RPG Maker MZ/MV project to manage character assets and integrate game information.

Instructions

Get all actors from the RPG Maker MZ/MV project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The 'getActors' function in 'src/tools/actorTools.ts' retrieves all actors from the project by reading 'Actors.json'.
    export async function getActors(projectPath: string): Promise<Actor[]> {
      const actorsPath = getDataPath(projectPath, 'Actors.json');
      return await readJsonFile<Actor[]>(actorsPath);
    }
  • src/index.ts:99-106 (registration)
    The 'get_actors' tool definition is registered in the 'getToolDefinitions' method in 'src/index.ts'.
    {
      name: 'get_actors',
      description: 'Get all actors from the RPG Maker MZ/MV project',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • The 'get_actors' tool handler in 'src/index.ts' calls 'actorTools.getActors' to execute the request.
    case 'get_actors':
      return await actorTools.getActors(this.projectPath);
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Get' implies a read-only operation, the description fails to mention the return format, potential payload size concerns when retrieving 'all' actors, or whether the operation is safe/destructive.

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 a single, efficiently structured sentence of seven words with no redundant or wasted text. The key information (action, scope, resource, domain) is front-loaded.

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 zero-parameter retrieval tool, the description is minimally adequate for selection purposes. However, given the lack of output schema and annotations, the absence of any description regarding what data fields constitute an 'actor' or the return structure leaves a noticeable gap.

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 and the schema coverage is 100% vacuously. Per the rubric, this establishes a baseline score of 4, as there are no parameter semantics to describe beyond what the empty schema already communicates.

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 uses a specific verb 'Get' and resource 'actors' with clear scope 'all' and domain context 'RPG Maker MZ/MV project'. However, it does not explicitly differentiate from siblings like 'get_actor' (singular) or 'search_actors' (filtered) in the text itself, relying solely on naming conventions.

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. It does not mention that 'get_actor' retrieves a single actor, 'search_actors' allows filtering, or when to prefer this unfiltered retrieval over those options.

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