Skip to main content
Glama

klyo games: publish HTML5 browser games

by pl.klyo
OverviewDiscussionsAdmin

Translate a game's texts (owner's own AI)

klyo_game_translate

Translations of a game's texts into the klyo languages (pl, en, de, fr, es, pt, it, ru, uk, tr). YOU TRANSLATE: the owner's assistant, on the owner's own AI plan; klyo runs no model and does not pay for translation. Two steps in one tool: (1) call with only slug to get the original field by field (oryginal), the original language, the languages still to do (do_tlumaczenia, with their state) and the check rules; (2) call with slug and tlumaczenia = { language code: { field: text } } with ALL the fields from oryginal. Each language goes through the same check as the developer's own text: long dashes and the ellipsis character are replaced with plain ones, no markup, no longer than twice the original, name and tagline on one line up to 80 characters, the text must be in that language, no disallowed words. A language that fails comes back in odrzucone with the reason: fix it and send it again; good languages are saved. What is saved are PROPOSALS: the owner approves them in the studio (dev.klyo.pl, the game, Translations) and only approved ones count for Google. Do not tell the user the translations are already on the page. This tool does not change the developer's own texts (English required, Polish for XP); that is klyo_fix_game.

Examples: • Translate my game into all klyo languages • What is missing in the translations of lantern-thief? • Add German and French versions of my game's description

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesGame address, for example lantern-thief (from klyo_my_games).
tlumaczeniaNoOmit to see what to translate. When saving: language code (pl, en, de, fr, es, pt, it, ru, uk, tr) → an object with ALL the fields from `oryginal` (nazwa, haslo, opis, sterowanie_dotyk, sterowanie_klawiatura, czas_partii; only those the game has).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / slug / description
      Previous value: -"Adres gry, np. lantern-thief (z klyo_my_games)."New value: +"Game address, for example lantern-thief (from klyo_my_games)."
    • changedInput schema / properties / tlumaczenia / description
      Previous value: -"Pomiń, żeby zobaczyć, co przetłumaczyć. Przy zapisie: kod języka (pl, en, de, fr, es, pt, it, ru, uk, tr) → obiekt z KOMPLETEM pól z `oryginal` (nazwa, haslo, opis, sterowanie_dotyk, sterowanie_klawiatura, czas_partii — tylko te, które gra ma)."New value: +"Omit to see what to translate. When saving: language code (pl, en, de, fr, es, pt, it, ru, uk, tr) → an object with ALL the fields from `oryginal` (nazwa, haslo, opis, sterowanie_dotyk, sterowanie_klawiatura, czas_partii; only those the game has)."
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Despite no annotations (readOnlyHint=false, etc.), the description fully discloses the non-destructive proposal nature, the check rules, failure handling, and that nothing is saved as final until owner approval. It also clarifies that klyo runs no model and the owner pays for translation.

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?

The description is long but well structured with clear steps and rules. It is front-loaded with the purpose and key constraints. However, some repetition of check rules could be condensed, but overall it is organized and each part adds value.

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

Completeness5/5

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

Given the complexity (two-step, multiple languages, validation rules), the description provides all necessary information: the workflow, the fields, the checks, the failure handling, and the approval process. No output schema exists, but the description explains what comes back (odrzucone, saved proposals).

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 schema covers the parameters well (100% coverage). The description adds context on the structure of tlumaczenia (all fields from oryginal) and the meaning of languages, but does not add new parameter-specific syntax details beyond schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('translate') and resource ('a game's texts'), and explains the two-step process. It clearly distinguishes from sibling klyo_fix_game by noting it does not change the developer's own texts.

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

Usage Guidelines5/5

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

It explicitly defines the two-step workflow, when to call with only slug vs with tlumaczenia, and provides example queries. It also states what not to do ('Do not tell the user the translations are already on the page').

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All klyo games: publish HTML5 browser games toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources