Remix Games

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.

Input Schema

Name	Required	Description	Default
`genre`	No	A Remix genre, such as puzzle, racing, match-3, soccer or roguelite
`limit`	No	How many games to return
`madeFor`	No	Only games made for this device. Every game also plays in a computer browser on remix.gg.	any

Output Schema

Name	Required	Description	Default
`games`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 25, 2026
- 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"
+]
```
First observedOct 2, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With readOnlyHint and destructiveHint=false already present, the description adds useful behavioral context: results are free, quick to start, staff-picks-first, and genre-ranked by most played. It does not discuss auth, rate limits, or pagination, but those are not clearly needed for this discovery tool.

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 description is two sentences, front-loads the usage condition, and then explains the returned result set. The examples earn their place by clarifying ambiguous natural-language requests.

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 that annotations cover safety and an output schema exists, the description supplies what an agent still needs: when to choose this tool, what kind of games it returns, and how results are prioritized. No important selection or invocation detail is missing.

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 schema already documents genre, limit, and madeFor. The description adds meaningful semantics by saying genre is optional and that genre results are ordered after staff picks, while its device examples reinforce madeFor usage.

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 states a specific recommendation behavior: free, quick-to-start browser games on remix.gg, with staff picks first and optionally genre-filtered. It also distinguishes the tool from name-based search by saying it is for when the user wants a game without naming one.

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?

It gives a clear triggering condition and several concrete user phrasings, such as quick puzzle games, phone games, and computer racing games. It does not explicitly name alternatives like search_games, but the 'without naming one' condition provides strong implied routing guidance.

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

All Remix Games tools Inspect

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

Need Help?