Skip to main content
Glama
garuh143

RPG Maker MZ/MV MCP Server

by garuh143

get_actor

Retrieve a specific actor by ID from RPG Maker MZ/MV projects to access character data for game development and management.

Instructions

Get a specific actor by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actorIdYesThe ID of the actor to retrieve

Implementation Reference

  • The handler function that retrieves a specific actor by ID from the list of actors.
    export async function getActor(projectPath: string, actorId: number): Promise<Actor | null> {
      const actors = await getActors(projectPath);
      return actors.find(actor => actor && actor.id === actorId) || null;
    }
  • The MCP tool definition and input schema for 'get_actor'.
    name: 'get_actor',
    description: 'Get a specific actor by ID',
    inputSchema: {
      type: 'object',
      properties: {
        actorId: {
          type: 'number',
          description: 'The ID of the actor to retrieve',
        },
      },
  • src/index.ts:660-661 (registration)
    The tool handler registration/dispatch logic in the main MCP request handler.
    case 'get_actor':
      return await actorTools.getActor(this.projectPath, args.actorId);
Behavior2/5

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

No annotations provided, so description carries full burden. 'Get' implies read-only, but description doesn't confirm safety, idempotency, or error behavior (null vs exception when actor missing). No mention of return structure.

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?

Extremely concise single sentence with no filler. However, given lack of annotations and output schema, slightly more content (error handling, sibling differentiation) would improve utility without violating conciseness.

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 single-parameter read operation with full schema coverage. Gaps remain regarding error handling and output format given no output schema exists, but core invocation path is documented.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 100% coverage with clear description of 'actorId'. Description adds no additional parameter context (e.g., ID format, valid ranges), but baseline 3 is appropriate given complete schema documentation.

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 ('actor'), and scope ('by ID'). Implicitly distinguishes from sibling 'get_actors' by specifying 'specific' and ID-based lookup, though it doesn't explicitly name sibling alternatives.

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 on when to use this versus 'get_actors' (plural fetch) or 'search_actors' (filtered query). Missing guidance on error cases (e.g., invalid ID not found).

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