Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
GEMINI_API_KEYNoYour Gemini API key (required for AI image generation and scenario generation features)

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
list_projectsC

List all RPG Maker MZ projects in a directory

read_project_infoC

Read RPG Maker MZ project information (Game.rpgproject file)

list_mapsC

List all maps in an RPG Maker MZ project

read_mapC

Read a specific map file from an RPG Maker MZ project

list_pluginsC

List all plugins in an RPG Maker MZ project

generate_project_contextC

Generate comprehensive context documentation for an RPG Maker MZ project including structure, maps, events, and plugin information

analyze_project_structureC

Analyze RPG Maker MZ project structure and provide insights about maps, connections, events, and game flow

extract_game_design_patternsC

Extract common game design patterns from the project (event patterns, map layouts, etc.)

create_projectB

Create a new RPG Maker MZ project from scratch

create_mapC

Create a new map in the project

update_map_tileC

Update a tile on a map

add_eventC

Add a new event to a map

add_event_commandC

Add a command to an event page (e.g., show text, transfer player, etc.)

add_actorC

Add a new actor to the database

add_classC

Add a new class to the database

add_skillC

Add a new skill to the database

add_itemC

Add a new item to the database

update_databaseC

Update an entry in any database (Actors, Classes, Skills, Items, Weapons, Armors, etc.)

generate_assetC

Generate RPG Maker MZ asset using Gemini 2.5 Flash (characters, faces, tilesets, etc.)

generate_asset_batchC

Generate multiple RPG Maker MZ assets in batch

describe_assetC

Analyze and describe an existing RPG Maker MZ asset using Gemini 2.5 Flash

generate_scenarioC

Generate a complete RPG game scenario using Gemini AI (story, maps, characters, events, items)

implement_scenarioC

Implement a generated scenario into the RPG Maker MZ project

generate_and_implement_scenarioC

Generate and immediately implement a complete RPG scenario (all-in-one)

generate_scenario_variationsC

Generate multiple variations of a scenario for comparison

autonomous_create_gameA

Autonomously create a complete RPG game from a concept. This tool orchestrates all game creation steps: project setup, scenario generation, battle system, quests, assets, balancing, and optimization. Perfect for rapid game prototyping with minimal input.

register_resourceC

Register a resource (template, asset, data) for reuse across the project

register_prompt_templateC

Register a reusable prompt template with variable placeholders and resource references

execute_promptC

Execute a prompt template with provided variables and resource references

list_resourcesB

List all registered resources with optional filtering

search_databaseC

Search game database (actors, enemies, skills, items, etc.) with filters

analyze_assetsC

Analyze all project assets, detect usage, find unused assets, and generate optimization recommendations

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3/5.0

Scored across 32 tools

Disambiguation3/5

Most tools have distinct purposes, but there is notable overlap between scenario-related tools (e.g., generate_scenario, generate_and_implement_scenario, implement_scenario) and asset-related tools (e.g., generate_asset, generate_asset_batch, describe_asset), which could cause confusion. However, descriptions clarify some distinctions, such as generate_and_implement_scenario being an all-in-one tool versus generate_scenario and implement_scenario being separate steps.

Naming Consistency4/5

Tool names largely follow a consistent verb_noun pattern (e.g., add_actor, create_map, list_maps), with minor deviations like autonomous_create_game (adjective_verb_noun) and analyze_assets (verb_noun_plural). The naming is readable and predictable overall, though not perfectly uniform.

Tool Count3/5

With 32 tools, the count feels heavy for an RPG Maker MZ server, as many tools could be consolidated (e.g., multiple scenario and asset tools). While the domain is broad, the toolset includes redundant or overlapping functionalities that bloat the count beyond a well-scoped range of 3-15 tools.

Completeness4/5

The toolset provides comprehensive coverage for RPG Maker MZ game development, including CRUD operations for databases, maps, and events, as well as analysis, generation, and implementation features. Minor gaps exist, such as no explicit tools for deleting or updating events or actors, but agents can likely work around these using update_database or similar tools.