Skip to main content
Glama
Sign In
RPG Maker MZ Authoring MCP

RPG Maker MZ Authoring MCP

by NixonMSilva
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Find references to a record

database_find_references
Read-onlyIdempotent

Find every known reference to a database record by category and ID across events, common events, troops, and other records before deleting or repurposing it.

Instructions

Every known reference to a record from events, common events, troops and other records (run before deleting or repurposing a record).

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": {
      "category": "<category>",
      "id": "<id>"
    },
    "name": "database_find_references"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
categoryYesDatabase category

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive behavior, so the description's main addition is the set of reference sources it scans and the safe-delete workflow. It says nothing about whether results are exhaustive, ordered, or paginated, leaving the read's output behavior opaque.

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?

A single front-loaded sentence with the scope first and the usage hint in a parenthetical; nothing is wasted. The parenthetical is slightly buried but does not impede comprehension.

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 two-parameter read-only lookup this covers purpose and workflow, but with no output schema the agent gets no hint of what a 'reference' looks like in the response. Combined with an undescribed 'id' parameter, the definition leaves real gaps for correct invocation.

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

Parameters2/5

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

Schema coverage is 50% (only 'category' is described, as 'Database category' with an enum; 'id' has no description at all). The description adds no meaning to either parameter — it never explains that 'id' is interpreted per category or that 'category' selects which record table is scanned, so it fails to compensate for the coverage gap.

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 ('Every known reference to a record') plus the source scope (events, common events, troops, other records). It is clearly distinguishable from CRUD siblings, though it does not address the separate 'find_references' sibling.

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

Usage Guidelines4/5

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

The parenthetical 'run before deleting or repurposing a record' gives a concrete when-to-use trigger. It stops short of naming any alternative tool or any when-not condition, so it is clear context without exclusions.

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