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

RPG Maker MZ Authoring MCP

by NixonMSilva
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Database templates

database_list_templates
Read-onlyIdempotent

Lists available database record templates and their parameters for record creation, helping you select the correct template and inputs.

Instructions

Record templates for database_create_record (template + templateParams).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "database_list_templates"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is fully covered. The description's added value is signaling that the return value feeds database_create_record's 'template' and 'templateParams' arguments, which is genuinely useful, but it says nothing about how templates are sourced, scoped, or how many may come back.

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 short sentence with no filler and the key noun front-loaded. It is a fragment rather than a full sentence, which makes it terse but slightly telegraphic for an agent with no prior context.

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, read-only tool this is close to adequate, and annotations plus the downstream-use hint cover most of what an agent needs. With no output schema, though, the description should say more about the shape of the returned template list (identifiers, names, structure of templateParams) than the two bare field names it offers.

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 takes zero parameters, so there is no parameter semantics to explain and the baseline is 4. The description does add a small amount by naming the two fields ('template' and 'templateParams') that the returned data maps onto in the consuming tool.

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 concrete resource ('Record templates') and ties it to a specific consumer ('for database_create_record'), so an agent knows this is a read-only template catalog. It does not explicitly distinguish itself from the sibling 'list_event_templates', but the resource and consumer are specific enough to separate them in practice.

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?

The parenthetical '(template + templateParams)' implies the intended workflow: call this first, then pass results into database_create_record. However, it never says when to call it versus 'list_event_templates' or other list siblings, and there is no explicit 'call this before creating a record' instruction.

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