Skip to main content
Glama
Sign In

klyo games: publish HTML5 browser games

by pl.klyo
OverviewDiscussionsAdmin

Write the creator's profile card (owner's own AI)

klyo_creator_card
Destructive

The developer's profile card on games.klyo.pl: “about me” and the tagline under the name. YOU WRITE: the owner's assistant, on the owner's own AI plan; klyo runs no model. Without o_mnie and haslo we return the current card, the released games (the only material you may write from) and the rules. With them, we save through the same check as the studio; an omitted field stays unchanged. Saving changes the developer's public page immediately and replaces the previous text, so FIRST show the text to the owner and save only with their consent. Do not invent facts about the person. pseudonim sets the author name players see; klyo_publish_game needs it (error wymaga_nazwy): ask the owner for the name and save it here, then retry.

Examples: • Write my developer profile card on klyo • Improve the tagline under my name on my developer page • What is in my profile card on games.klyo.pl now?

Input Schema

NameRequiredDescriptionDefault
hasloNoOne sentence up to 80 characters per language with no full stop; may have <pl>...</pl><en>...</en>, each version counted on its own. Keep it short: the Google title of the page is “Free {name}: {tagline}” (Polish “{nazwa} za darmo: {haslo}”) and must fit 59 characters, otherwise the page gets the generic “{name}: play free online”; do not repeat free/za darmo, the template adds it. The tool answer `do_poprawy` shows the resulting title per language. Omit to leave it as it is.
o_mnieNo“About me” in the first person; two versions in tags <pl>…</pl><en>…</en>. Omit to only read.
pseudonimNoThe name players see as the author of the developer's games, posts and clips (2 to 30 characters). Required before klyo_publish_game when the account has no name (error `wymaga_nazwy`). ASK THE OWNER for it, never make one up.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / pseudonim
      Added value: +{
+  "description": "The name players see as the author of the developer's games, posts and clips (2 to 30 characters). Required before klyo_publish_game when the account has no name (error `wymaga_nazwy`). ASK THE OWNER for it, never make one up.",
+  "maxLength": 30,
+  "minLength": 2,
+  "type": "string"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / haslo / description
      Previous value: -"One sentence up to 80 characters per language with no full stop; may have <pl>...</pl><en>...</en>, each version counted on its own. Omit to leave it as it is."New value: +"One sentence up to 80 characters per language with no full stop; may have <pl>...</pl><en>...</en>, each version counted on its own. Keep it short: the Google title of the page is “Free {name}: {tagline}” (Polish “{nazwa} za darmo: {haslo}”) and must fit 59 characters, otherwise the page gets the generic “{name}: play free online”; do not repeat free/za darmo, the template adds it. The tool answer `do_poprawy` shows the resulting title per language. Omit to leave it as it is."
  3. Changed2 schema fields changed
    • changedInput schema / properties / haslo / description
      Previous value: -"One sentence up to 80 characters with no full stop; may have <pl>…</pl><en>…</en>. Omit to leave it as it is."New value: +"One sentence up to 80 characters per language with no full stop; may have <pl>...</pl><en>...</en>, each version counted on its own. Omit to leave it as it is."
    • changedInput schema / properties / haslo / maxLength
      Previous value: -90New value: +400
  4. Changed2 schema fields changed
    • changedInput schema / properties / haslo / description
      Previous value: -"Jedno zdanie do 80 znaków bez kropki; może mieć <pl>…</pl><en>…</en>. Pomiń, żeby zostało, jak jest."New value: +"One sentence up to 80 characters with no full stop; may have <pl>…</pl><en>…</en>. Omit to leave it as it is."
    • changedInput schema / properties / o_mnie / description
      Previous value: -"„O mnie” w pierwszej osobie; dwie wersje w znacznikach <pl>…</pl><en>…</en>. Pomiń, żeby tylko odczytać."New value: +"“About me” in the first person; two versions in tags <pl>…</pl><en>…</en>. Omit to only read."
  5. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false; the description goes well beyond by stating the save replaces the previous text and changes the public page immediately, that saves pass through the same validation as the studio, and that the calling assistant (not klyo) authorizes the write. The read-mode behavior is also disclosed, resolving a real ambiguity left by the non-readOnly annotation.

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?

Front-loads the resource and then the write/read contract, with no filler sentences. It is dense — capitalized 'YOU WRITE', interleaved Polish field names, and a trailing example block make it slightly harder to scan than needed for a 3-parameter tool.

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?

No output schema exists, and the description compensates: it says exactly what the read mode returns (current card, the released games as the only permitted source material, and the rules) and references the `do_poprawy` response field. Combined with the consent gate and mutation warning, an agent has everything needed to call it safely.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the schema already documents the tagline length/title-template rules, the `<pl>/<en>` tagging, the omit-to-keep behavior, and the `wymaga_nazwy` requirement. The description restates these rather than adding new semantics, so the 3 baseline applies.

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

Purpose4/5

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

States the concrete resource (the developer profile card on games.klyo.pl: 'about me' plus the tagline) and immediately clarifies the dual mode — read when `o_mnie`/`haslo` are omitted, write when supplied. It does not explicitly contrast itself with siblings like `klyo_update_game` or `klyo_add_post`, but it does describe the handoff to `klyo_publish_game`, so an agent can place it.

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?

Gives explicit mode selection rules (no fields = read, fields = save, omitted field = unchanged), a mandatory workflow gate ('FIRST show the text to the owner and save only with their consent'), a content constraint ('Do not invent facts about the person'), and a cross-tool retry instruction tied to `klyo_publish_game` error `wymaga_nazwy`.

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