Skip to main content
Glama

klyo games: publish HTML5 browser games

by pl.klyo
OverviewDiscussionsAdmin

Release the waiting version of a game

klyo_release_version

Release to players the version waiting after klyo_update_game (slug). Same step as the “Release” button in the studio: players get the new version at once (anyone in the middle of a round sees a bar “update or finish the round”), the previous version stays with us, the game page is rebuilt and the developer's followers are notified. You may omit the kind of change (zmiana); then we use the one measured from the files. Effect on the clip: poprawka (fix): the clip stays; funkcja (feature): the clip stays and nowosc (one sentence) goes to the feed as “New”; interfejs (interface): the old clip leaves the tile and the feed until a person records a new one in the studio (the assistant does not record clips). Release only when the owner has confirmed that they played the new version, or deliberately wants to release it without playing. PREMIUM REVIEW: for any change other than poprawka, pass przeglad (seven points with evidence, listed in the schema and in klyo_game_requirements); before the swap the whole game goes through the check again.

Examples: • Release the new version of lantern-thief, it is a fix • I played it and it works: release the version with the new feature, a daily mode • Release the waiting version of my game

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesGame address on the account, for example lantern-thief (from klyo_my_games).
nowoscNoWhat is new: one sentence for the clip card in the feed. Only with `funkcja`.
zmianaNoKind of change: `poprawka` = fix (the clip stays) | `funkcja` = feature (the clip stays, `nowosc` goes to the feed) | `interfejs` = interface (the old clip is taken down until a new one is recorded). Omitted = the kind measured from the files (`podpowiedz` from klyo_update_game).
przegladNoPremium quality review, seven points with evidence. Required unless `zmiana` is `poprawka` (a fix). The server does not judge taste; it matches the declaration against traces in the code and shows it to the owner before “Release”.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / nowosc / description
      Previous value: -"Co nowego — jedno zdanie na kartę klipu w feedzie. Tylko przy `funkcja`."New value: +"What is new: one sentence for the clip card in the feed. Only with `funkcja`."
    • addedInput schema / properties / przeglad
      Added value: +{
+  "additionalProperties": false,
+  "description": "Premium quality review, seven points with evidence. Required unless `zmiana` is `poprawka` (a fix). The server does not judge taste; it matches the declaration against traces in the code and shows it to the owner before “Release”.",
+  "properties": {
+    "animacja": {
+      "additionalProperties": false,
+      "description": "PASS means: Every state change has a 120 to 300 ms transition, screens enter and leave, there is a win and a lose animation. Motion switches off with prefers-reduced-motion.",
+      "properties": {
+        "dowod": {
+          "description": "What exactly was done: file, function, what is visible on screen.",
+          "maxLength": 400,
+          "minLength": 20,
+          "type": "string"
+        },
+        "stan": {
+          "enum": [
+            "pass"
+          ],
+          "type": "string"
+        }
+      },
+      "required": [
+        "stan",
+        "dowod"
+      ],
+      "type": "object"
+    },
+    "dzwiek": {
+      "additionalProperties": false,
+      "description": "PASS means: Sound for every player action and every result (tap, error, win), mute in the settings, resumes after returning from the background.",
+      "properties": {
+        "dowod": {
+          "description": "What exactly was done: file, function, what is visible on screen.",
+          "maxLength": 400,
+          "minLength": 20,
+          "type": "string"
+        },
+        "stan": {
+          "enum": [
+            "pass"
+          ],
+          "type": "string"
+        }
+      },
+      "required": [
+        "stan",
+        "dowod"
+      ],
+      "type": "object"
+    },
+    "grafika": {
+      "additionalProperties": false,
+      "description": "PASS means: One art direction: one palette, one style of outlines and corners, background, scene and elements from one skin (Klyo Kit: gra.skora, gra.rysuj, gra.generuj). No bare rectangles on a gradient. Readable on a phone in full sunlight.",
+      "properties": {
+        "dowod": {
+          "description": "What exactly was done: file, function, what is visible on screen.",
+          "maxLength": 400,
+          "minLength": 20,
+          "type": "string"
+        },
+        "stan": {
+          "enum": [
+            "pass"
+          ],
+          "type": "string"
+        }
+      },
+      "required": [
+        "stan",
+        "dowod"
+      ],
+      "type": "object"
+    },
+    "informacja_zwrotna": {
+      "additionalProperties": false,
+      "description": "PASS means: Every action gets a response within 100 ms: picture and sound, and vibration on a phone. It is clear whose move it is, a move is previewed before it is released, and the reason a move is not allowed is shown.",
+      "properties": {
+        "dowod": {
+          "description": "What exactly was done: file, function, what is visible on screen.",
+          "maxLength": 400,
+          "minLength": 20,
+          "type": "string"
+        },
+        "stan": {
+          "enum": [
+            "pass"
+          ],
+          "type": "string"
+        }
+      },
+      "required": [
+        "stan",
+        "dowod"
+      ],
+      "type": "object"
+    },
+    "jezyki": {
+      "additionalProperties": false,
+      "description": "PASS means: All texts from the translation table (at least Polish and English), the language from the device settings, no text written into the drawing code. `nie_dotyczy` (not applicable) only for a game without words.",
+      "properties": {
+        "dowod": {
+          "description": "What exactly was done: file, function, what is visible on screen.",
+          "maxLength": 400,
+          "minLength": 20,
+          "type": "string"
+        },
+        "stan": {
+          "enum": [
+            "pass",
+            "nie_dotyczy"
+          ],
+          "type": "string"
+        }
+      },
+      "required": [
+        "stan",
+        "dowod"
+      ],
+      "type": "object"
+    },
+    "motyw": {
+      "additionalProperties": false,
+      "description": "PASS means: Light and dark variant following prefers-color-scheme plus a switch in the settings; both checked on screenshots.",
+      "properties": {
+        "dowod": {
+          "description": "What exactly was done: file, function, what is visible on screen.",
+          "maxLength": 400,
+          "minLength": 20,
+          "type": "string"
+        },
+        "stan": {
+          "enum": [
+            "pass"
+          ],
+          "type": "string"
+        }
+      },
+      "required": [
+        "stan",
+        "dowod"
+      ],
+      "type": "object"
+    },
+    "online": {
+      "additionalProperties": false,
+      "description": "PASS means: A game for two or more people: invitation by link, a “waiting for the opponent” state, disconnect and return, a rematch with one gesture. `nie_dotyczy` (not applicable) for a solo game, with the reason.",
+      "properties": {
+        "dowod": {
+          "description": "What exactly was done: file, function, what is visible on screen.",
+          "maxLength": 400,
+          "minLength": 20,
+          "type": "string"
+        },
+        "stan": {
+          "enum": [
+            "pass",
+            "nie_dotyczy"
+          ],
+          "type": "string"
+        }
+      },
+      "required": [
+        "stan",
+        "dowod"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "grafika",
+    "animacja",
+    "dzwiek",
+    "informacja_zwrotna",
+    "motyw",
+    "jezyki",
+    "online"
+  ],
+  "type": "object"
+}
    • changedInput schema / properties / slug / description
      Previous value: -"Adres gry na koncie, np. lantern-thief (z klyo_my_games)."New value: +"Game address on the account, for example lantern-thief (from klyo_my_games)."
    • changedInput schema / properties / zmiana / description
      Previous value: -"Rodzaj zmiany: poprawka (klip zostaje) | funkcja (klip zostaje, `nowosc` do feedu) | interfejs (stary klip schodzi do czasu nagrania nowego). Pominięte = rodzaj zmierzony z plików (`podpowiedz` z klyo_update_game)."New value: +"Kind of change: `poprawka` = fix (the clip stays) | `funkcja` = feature (the clip stays, `nowosc` goes to the feed) | `interfejs` = interface (the old clip is taken down until a new one is recorded). Omitted = the kind measured from the files (`podpowiedz` from klyo_update_game)."
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the minimal annotations, the description discloses rich behavioral effects: players immediately get the new version, mid-round players see an update bar, the previous version stays, the game page is rebuilt, followers are notified, and clip behavior changes per `zmiana` type. It also describes the review re-check before the swap. This is exactly the kind of context annotations cannot convey.

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-organized: core operation, then parameter effects, then gating conditions, then the review requirement, then examples. Some material repeats schema content, but for a complex release operation that reinforcement is useful rather than wasteful.

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?

Despite having no output schema, the description fully covers what the agent needs to call the tool correctly: the prerequisite (waiting version from klyo_update_game), the eligibility condition (owner confirmation), when evidence is required, and all user-visible side effects. Nothing critical for invocation 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?

The schema already provides detailed parameter descriptions and covers 100% of parameters, so the baseline is 3. The description adds value by explaining the default for omitted `zmiana`, the clip consequences for each change type, the `nowosc` feed behavior, and the condition under which `przeglad` is mandatory.

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 opens with a specific action on a specific resource: 'Release to players the version waiting after klyo_update_game (`slug`)'. It clearly identifies this as the update-release step and distinguishes it from other game lifecycle tools by pointing at the upstream update tool.

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

Usage Guidelines4/5

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

It gives clear usage context: this tool is for releasing the waiting version after an update, and only when the owner has played the new version or deliberately waived that. It also states when a premium review is required. However, it does not explicitly tell the agent when not to use it or name alternatives such as klyo_publish_game or klyo_release_rollback.

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