Skip to main content
Glama

videogames

by io.github.pipeworx-io
OverviewDiscussionsAdmin

List Games

list_games
Read-onlyIdempotent

List free-to-play games from FreeToGame, optionally filtered by platform (pc/browser) and category (e.g., mmorpg, shooter, strategy) and sorted by release-date, popularity, or alphabetical. Returns all matching games.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sort_byNoSort order: "release-date", "popularity", "alphabetical", or "relevance"
categoryNoGenre/category filter, e.g. "mmorpg", "shooter", "strategy", "moba", "racing", "sports", "social", "sandbox", "open-world", "survival", "pvp", "pve", "pixel", "voxel", "zombie", "turn-based", "first-person", "third-person", "top-down", "tower-defense", "horror", "mmofps"
platformNoPlatform filter: "pc", "browser", or "all" (default "all")

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
gamesYes
totalYesTotal number of games returned

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "games": {
+      "items": {
+        "properties": {
+          "game_url": {
+            "description": "URL to play the game",
+            "type": "string"
+          },
+          "genre": {
+            "description": "Game genre",
+            "type": "string"
+          },
+          "id": {
+            "description": "Game ID",
+            "type": "number"
+          },
+          "platform": {
+            "description": "Platform availability",
+            "type": "string"
+          },
+          "publisher": {
+            "description": "Game publisher name",
+            "type": "string"
+          },
+          "release_date": {
+            "description": "Game release date",
+            "type": "string"
+          },
+          "short_description": {
+            "description": "Brief game description",
+            "type": "string"
+          },
+          "thumbnail": {
+            "description": "URL to game thumbnail image",
+            "type": "string"
+          },
+          "title": {
+            "description": "Game title",
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "title",
+          "short_description",
+          "game_url",
+          "genre",
+          "platform",
+          "publisher",
+          "release_date",
+          "thumbnail"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "description": "Total number of games returned",
+      "type": "number"
+    }
+  },
+  "required": [
+    "total",
+    "games"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "category": "shooter",
+    "platform": "pc",
+    "sort_by": "popularity"
+  },
+  {
+    "category": "strategy",
+    "platform": "browser"
+  }
+]
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, and non-destructive behavior, so the bar is lower. The description adds valuable context by specifying the data source (FreeToGame) and stating that it 'returns all matching games,' which implies no hidden pagination limits and sets expectations for output completeness.

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?

One succinct, front-loaded sentence covers all key aspects: the resource, source, optional filters, sort options, and return behavior. No wasted words; every phrase adds value.

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?

Given the tool's moderate complexity, the rich parameter schema, output schema availability, and comprehensive annotations, the description is complete. It covers source, filtering, sorting, and return semantics, so an agent has enough context to invoke it correctly.

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?

The schema description coverage is 100%, with each parameter already having a clear description of allowed values. The tool description restates the filterable fields and provides examples, but adds little beyond the schema. Baseline 3 is appropriate since schema does the heavy lifting.

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 uses a specific verb ('List') and resource ('free-to-play games from FreeToGame'), and clearly conveys the tool's scope via optional filters and sorting. This distinguishes it from siblings like get_game and filter_games, which target specific entities or more refined filtering.

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 implies when to use the tool (when you need a list of free-to-play games with optional filtering/sorting) but does not explicitly mention exclusions or alternatives. The sibling list makes it easy to infer, but there is no direct 'use X instead' guidance, so it falls short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All videogames 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