Skip to main content
Glama
Sign In
RPG Maker MV MCP Server

RPG Maker MV MCP Server

by Xerolo44
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get database record

get_record

Retrieves the full JSON of a single RPG Maker MV database record by ID and database type, so you can inspect actors, items, skills, or other project data.

Instructions

Get the full JSON of one database record by id.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "type": "<type>",
      "id": "<id>"
    },
    "name": "get_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesRecord id (1-based)
typeYesWhich database to access (e.g. actors, items, skills, troops, commonEvents)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.1

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. 'Full JSON' usefully signals that the complete record is returned rather than a summary, but it says nothing about read-only semantics (only implied), error behavior on a missing id, or whether related sub-records are expanded.

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?

A single front-loaded sentence with no filler; the key constraint ('one record by id') appears immediately.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A simple two-parameter read tool with a fully described schema and no output schema; 'full JSON' adequately sets the return expectation. A brief note on missing-id behavior or the record-type enum would make it complete.

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 description coverage is 100%, so the 'id' and 'type' semantics are already fully documented in the schema, including the 12-value enum. The description adds only the general notion of selecting by id, which is a baseline-3 contribution.

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 a specific verb and resource ('Get the full JSON of one database record by id'), naming both the object and the lookup key. It implicitly contrasts with list_records/search_records by stressing 'one' record, but never names an alternative explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: call it when you already know the record type and id. There is no statement of when to prefer search_records or list_records instead, and no note about what happens for a nonexistent id.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools