Skip to main content
Glama

Related Servers

Alternatives to gametrans

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to inspect and edit an RPG Maker MZ project through its real JSON data files, render maps to PNG previews so layouts can be seen rather than guessed, and decode event commands into named, parameter-labelled lines. It also drives a live playtest through a bridge plugin and authors whole maps, databases, events and assets via high-level tool calls.
      65
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to develop Banner of the Maid mods by reading and modifying game data (characters, items, weapons, skills, dialogue, saves, portraits) and to perform live in-game verification via launching the game, taking screenshots, and clicking by coordinates.
      2
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents, developers, and CI pipelines to run deterministic, offline localization QA — pseudolocalization, locale linting for separators/dates/placeholders/RTL, and glossary enforcement across 20 locales — without any network access or API key. When an OpenAI-compatible endpoint is configured, it can also translate into multiple locales and lint the results, or otherwise emit structured translation jobs instead of fabricating translations.
      4 npm
      MIT

    TDQS

    C2.9/5.0

    Scored across 61 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes and the detailed Chinese descriptions help distinguish operations. A few pairs like engine_options/engine_info, resource_term_add/resource_term_import, and graph_show/graph_dependencies have some overlap, but boundaries are generally discoverable.

    Naming Consistency4/5

    All names use snake_case, which is consistent. However, the set mixes prefixed tools (engine_, graph_, resource_) with bare verbs/nouns (pack, scan, translate, plan, staleness), and mixes verb-first with noun-first patterns.

    Tool Count1/5

    61 tools is an extreme mismatch for practical MCP scoping. Even for a complex localization pipeline, this imposes a very high selection and maintenance burden, far beyond the recommended 3-15 range.

    Completeness4/5

    The surface covers project setup, engine discovery, graph/dependency management, translation lifecycle, resource CRUD, UI/config, and agent queue operations. Minor gaps remain, such as project deletion or engine package lifecycle management, but core workflows are well covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues