Skip to main content
Glama

klyo games: publish HTML5 browser games

by pl.klyo
OverviewDiscussionsAdmin

Post in the games community

klyo_add_post

Write a post in the klyo games community: a question, a request for playtesters, a launch or a game showcase. The post is visible immediately, with no moderation queue, and can be linked to a game from the catalogue (gra_slug); then readers get a “play” button.

Examples: • Write a post on klyo about my game's launch • Ask for playtesters for my game on klyo games • Add a showcase of lantern-thief to the community

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
linkNoOptional: address of the game in a store or on another site.
jezykYesLanguage of the post.
trescYesPost text, at least 20 characters. Write like a person talking to people, without advertising slogans.
tytulYesPost title, 6 to 120 characters.
rodzajYes`pytanie` = question | `test` = request for playtesters | `premiera` = launch | `pokaz` = showcase.
gra_slugNoOptional: the catalogue game the post is about.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / gra_slug / description
      Previous value: -"Opcjonalnie: gra z katalogu, do której wpis się odnosi."New value: +"Optional: the catalogue game the post is about."
    • changedInput schema / properties / jezyk / description
      Previous value: -"Język wpisu."New value: +"Language of the post."
    • changedInput schema / properties / link / description
      Previous value: -"Opcjonalnie: adres gry w sklepie albo na innej stronie."New value: +"Optional: address of the game in a store or on another site."
    • changedInput schema / properties / rodzaj / description
      Previous value: -"pytanie | test (prośba o testy) | premiera | pokaz."New value: +"`pytanie` = question | `test` = request for playtesters | `premiera` = launch | `pokaz` = showcase."
    • changedInput schema / properties / tresc / description
      Previous value: -"Treść wpisu, od 20 znaków. Pisz jak człowiek do ludzi, bez haseł reklamowych."New value: +"Post text, at least 20 characters. Write like a person talking to people, without advertising slogans."
    • changedInput schema / properties / tytul / description
      Previous value: -"Tytuł wpisu, 6–120 znaków."New value: +"Post title, 6 to 120 characters."
  2. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only indicate non-read-only and non-destructive, leaving the tool's write nature implied. The description adds valuable behavioral details: the post appears immediately with no moderation queue, and linking to a game adds a play button. This goes beyond the annotations and helps the agent anticipate the outcome.

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 compact, with a clear main purpose stated first, followed by a key behavioral note and three illustrative examples. It avoids redundancy and is well-organized for quick scanning, though it could be slightly more streamlined.

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

Completeness4/5

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

For a 6-parameter tool, the description covers the core purpose, the immediate visibility, the linking effect, and typical use cases. It does not detail error handling or return values, but the absence of an output schema and the simplicity of the operation make this acceptable. Overall, an agent can confidently invoke the tool.

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 the baseline is 3. The description adds semantic value beyond the schema by explaining the effect of gra_slug (readers get a play button) and by contextualizing the post types with examples. This extra guidance justifies a 4.

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 clearly states the tool writes a post in the klyo games community and enumerates the specific post types (question, playtesters, launch, showcase). This is a distinct resource and verb, and it is unambiguous compared to sibling tools that all handle game management rather than community posting.

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?

The description provides concrete examples of when to use the tool (launch, playtesting, showcase) and explains the immediate visibility and linking behavior. It does not explicitly name alternative tools or exclusions, but since no sibling tool serves the same purpose, the usage context is sufficiently clear.

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