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

RPG Maker MZ Authoring MCP

by NixonMSilva
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Search database records

database_search_records
Read-onlyIdempotent

Find specific RPG Maker MZ database records by searching names, notes, descriptions, or metadata across categories, enabling targeted lookups for actors, items, and skills.

Instructions

Search records by name, note, description or note-tag metadata across one or more categories.

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": {
      "text": "<text>"
    },
    "name": "database_search_records"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
limitNo
fieldsNo
categoriesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds nothing beyond that: it says nothing about match semantics (substring vs fuzzy vs case sensitivity), whether multiple fields are OR'd or AND'd, default category scope, or how limit truncates results.

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 no filler, and the search scope leads. It is efficient, though 'note-tag metadata' is a slightly opaque label for the 'meta' field value and the sentence stops before the useful operational detail.

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

Completeness2/5

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

With four undocumented parameters, no output schema, and no parameter descriptions in the schema itself, the definition is too thin for an agent to call it confidently. The agent must guess match semantics, limit behavior, and default field/category scope.

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 description coverage is 0%, so the description must carry parameter meaning, and it only partly does. It clarifies that the query matches against name/note/description/meta (the 'fields' enum) and that categories can be plural, but it never explains the required 'text' matching behavior or the 'limit' parameter (cap 500, negative minimum).

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 ('Search') and resource ('records') and names the searched surfaces (name, note, description, note-tag metadata) plus the category scoping. That is enough to separate it from database_get_record and database_list_records, though it never names those siblings explicitly.

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 when-to-use or when-not-to-use guidance is given. The agent is left to infer that this is the text-query option versus database_list_records or database_find_references, and nothing tells it when a search is the wrong choice.

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