Skip to main content
Glama

Remix staff picks

top_games
Read-only

Use this when the user wants a game to play without naming one, such as "find me a quick puzzle game", "something fun to play on my phone" or "racing games for my computer". Returns free, quick-to-start browser games on remix.gg, Remix staff picks first, optionally in one genre, then that genre's most played.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "top_games"
  }
}

Input Schema

NameRequiredDescriptionDefault
genreNoA Remix genre, such as puzzle, racing, match-3, soccer or roguelite
limitNoHow many games to return
madeForNoOnly games made for this device. Every game also plays in a computer browser on remix.gg.any

Output Schema

NameRequiredDescriptionDefault
gamesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / genre / enum
      Previous value: -[
      -  "action",
      -  "adventure",
      -  "basketball",
      -  "board",
      -  "card",
      -  "casual",
      -  "clicker",
      -  "cooking",
      -  "driving",
      -  "education",
      -  "fighting",
      -  "flying",
      -  "football",
      -  "golf",
      -  "kids",
      -  "match-3",
      -  "music",
      -  "platformer",
      -  "puzzle",
      -  "racing",
      -  "roguelite",
      -  "rpg",
      -  "shooter",
      -  "simulation",
      -  "soccer",
      -  "sports",
      -  "strategy",
      -  "trivia",
      -  "word"
      -]New value: +[
      +  "action",
      +  "adventure",
      +  "basketball",
      +  "board",
      +  "card",
      +  "casual",
      +  "clicker",
      +  "cooking",
      +  "driving",
      +  "education",
      +  "fighting",
      +  "flying",
      +  "football",
      +  "golf",
      +  "kids",
      +  "match-3",
      +  "merge",
      +  "music",
      +  "platformer",
      +  "puzzle",
      +  "racing",
      +  "roguelite",
      +  "rpg",
      +  "shooter",
      +  "simulation",
      +  "soccer",
      +  "sports",
      +  "strategy",
      +  "trivia",
      +  "word"
      +]
  2. Changed4 schema fields changed
    • removedOutput schema / properties / games / items / properties / creator / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / games / items / properties / creator / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / games / items / properties / imageUrl / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / games / items / properties / imageUrl / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover read-only/safe/non-open-world, and the description adds real substance on top: results are free, quick to start, staff-picks-first, then padded by genre most-played. The ordering/curation behavior is the key non-obvious trait and it is disclosed.

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?

Two sentences, front-loaded with the when-to-use trigger and followed by exactly what is returned. No filler and no restatement of the title or name.

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?

Output schema exists and annotations cover the safety profile, so the description only needs to explain selection logic, which it does. Minor gap: it does not hint at result count or that the list may be short when a niche genre has few staff picks.

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, but the description adds meaning beyond the schema by explaining the ordering consequence of supplying a genre. The madeFor parameter is demonstrated through the "on my phone" / "for my computer" examples; only limit is left entirely to 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?

States a specific verb and resource: "Returns free, quick-to-start browser games on remix.gg" with an explicit curation rule (staff picks first, then genre most-played). It carves out the search case implicitly with "without naming one," which distinguishes it from search_games, though it never names the sibling.

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?

Gives clear triggering conditions with three concrete example utterances (quick puzzle game, phone game, computer racing), which map well onto the actual parameters. It does not name search_games or get_game as alternatives or state when not to use this tool.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources