Skip to main content
Glama

klyo games: publish HTML5 browser games

by pl.klyo
OverviewDiscussionsAdmin

Game statistics

klyo_game_stats
Read-onlyIdempotent

Visits to the game page and plays, day by day, for the given game (slug). Read-only. The developer's share of ad revenue is calculated from this.

Examples: • How many people played my game this week? • Stats for lantern-thief • Show plays day by day

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dniNoHow many days of the daily series (default 30).
slugYesGame address in the catalogue, for example lantern-thief (from klyo_my_games).
sprawdz_googleNoAsk Google about this game's pages now (URL Inspection), at most once an hour per game. Each page then carries `sprawdzono` (when we asked) and `odwiedziny` (Google's last crawl). Google has no API to request indexing of an ordinary page: the sitemap already submits it, and the Request indexing button lives in Search Console.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / dni
      Added value: +{
+  "description": "How many days of the daily series (default 30).",
+  "maximum": 365,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / sprawdz_google
      Added value: +{
+  "description": "Ask Google about this game's pages now (URL Inspection), at most once an hour per game. Each page then carries `sprawdzono` (when we asked) and `odwiedziny` (Google's last crawl). Google has no API to request indexing of an ordinary page: the sitemap already submits it, and the Request indexing button lives in Search Console.",
+  "type": "boolean"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / slug / description
      Previous value: -"Adres gry w katalogu, np. lantern-thief (z klyo_my_games)."New value: +"Game address in the catalogue, for example lantern-thief (from klyo_my_games)."
  3. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the description carries little safety burden. It adds the 'day by day' granularity and the revenue context, but it does not describe response format or behavior beyond what the schema's sprawdz_google parameter already explains.

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

Conciseness5/5

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

The core purpose is front-loaded in the first sentence, and the examples are compact and useful. There is no fluff or repetition of schema-level detail.

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 read-only, idempotent stats tool with fully described parameters and no output schema, this is nearly complete: it states the metrics, granularity, scope, and safety. It lacks only an explicit note on response shape or pagination, which is a minor gap.

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 description coverage is 100%, so all parameters are fully documented in the schema. The description's examples illustrate slug use but add no meaning beyond the schema.

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?

The description clearly identifies what the tool returns: daily visits and plays for a specific game, with example queries showing intended use. It does not explicitly contrast this with siblings such as klyo_game_diagnostics, so some differentiation is left to inference.

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 examples like 'How many people played my game this week?' and the mention that ad revenue share is calculated from this data give clear usage context. It does not state explicit exclusions or alternatives, but the intended scenarios are easy to infer.

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