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. PAGE ADDRESS PER LANGUAGE: every language page of the game has its own address in that language (/de/spider-solitaer/, /uk/pasians-pavuk/), never the Polish one. Send adres with the language, or we derive it from the translated name; it is approved together with the texts and then stays stable (a later name change does not move it).

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). Optional `adres` (languages other than pl and en): the game page address in that language, lowercase Latin letters, digits and single hyphens, 2 to 60 characters, from the translated name (German "Spider Solitär" → spider-solitaer, Ukrainian "Пасьянс Павук" → pasians-pavuk). Without it we build it from the translated `nazwa`. A taken or reserved address comes back in `odrzucone`; after the owner approves, the old address redirects 301 to the new one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / tlumaczenia / description
      Previous 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)."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). Optional `adres` (languages other than pl and en): the game page address in that language, lowercase Latin letters, digits and single hyphens, 2 to 60 characters, from the translated name (German \"Spider Solitär\" → spider-solitaer, Ukrainian \"Пасьянс Павук\" → pasians-pavuk). Without it we build it from the translated `nazwa`. A taken or reserved address comes back in `odrzucone`; after the owner approves, the old address redirects 301 to the new one."
  2. 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)."
  3. Added

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations it discloses the whole behavioral contract: outputs are PROPOSALS requiring owner approval, failed languages return in `odrzucone` with reasons, addresses are stable after approval with a 301 redirect, and klyo runs no model. None of this is derivable from the {readOnlyHint:false, idempotentHint:false} annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded and every section carries real content, but it is delivered as a dense, run-on wall of all-caps fragments with no bullet or step separation, making it harder to scan than the complexity requires. Some of the validation rule text is verbose.

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?

For a moderately complex two-mode mutation tool with no output schema and nested objects, the description covers the return values (`oryginal`, `do_tlumaczenia`, `odrzucone`), the approval lifecycle, and address behavior. Nothing an agent needs to call it correctly is missing.

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?

Schema coverage is 100%, so both parameters are already documented; the description still adds flow semantics the schema cannot, namely 'omit `tlumaczenia` to see what to translate' and how `adres` interacts with approval. It largely complements rather than duplicates the 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?

It states a specific verb and resource ('Translations of a game's texts into the klyo languages') and even names the sibling it is not ('This tool does not change the developer's own texts... that is klyo_fix_game'). An agent can distinguish it from klyo_fix_game without opening either schema.

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 lays out the exact two-step workflow (call with only `slug`, then call with `slug` + `tlumaczenia`), names the alternative tool, and gives concrete trigger examples. It also states a when-not-to-report rule ('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