Skip to main content
Glama

Suggest free-to-play games

list_free_to_play
Read-only

Return free-to-play games, which cost nothing to play, most reviewed on Steam first. Use it when the reader wants something free; for paid games within a budget use find_games, and for discounts list_deals. genre (a Steam genre) and platform (pc, xbox, playstation or switch) narrow the list and combine; total is the full count, which can exceed limit. There are no prices and no promoted placements. The result also says where signed-in members claim the time-limited free-to-keep giveaways, which are not listed here. Each game links to its page on getcheapgames.com.

Input Schema

NameRequiredDescriptionDefault
genreNoA Steam genre, spelled as Steam spells it: Action, Adventure, Casual, Indie, Massively Multiplayer, Racing, RPG, Simulation, Sports or Strategy. Any other value matches nothing.
limitNoGames to return, 1-24. Defaults to 5.
countryNoTwo-letter market code, any case, e.g. de, gb, us, br or pl (40 markets). It decides the currency prices come back in, which keys count as region-locked, and the market every link opens in. Omitted or unsupported codes fall back to ie (Ireland, euro).
platformNoOnly keys for this platform: pc, xbox, playstation or switch. Omit for all.

Output Schema

NameRequiredDescriptionDefault
gamesYes
totalNo
marketNo
pageUrlNo
orderingNo
freeToKeepNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / country / description
      Previous value: -"Two-letter market code, e.g. de, gb, us, br. Decides the currency, which keys count as region-locked and the market every link points into. Defaults to ie (euro)."New value: +"Two-letter market code, any case, e.g. de, gb, us, br or pl (40 markets). It decides the currency prices come back in, which keys count as region-locked, and the market every link opens in. Omitted or unsupported codes fall back to ie (Ireland, euro)."
    • changedInput schema / properties / genre / description
      Previous value: -"A Steam genre, as Steam names it: Action, Adventure, Casual, Indie, Massively Multiplayer, Racing, RPG, Simulation, Sports or Strategy."New value: +"A Steam genre, spelled as Steam spells it: Action, Adventure, Casual, Indie, Massively Multiplayer, Racing, RPG, Simulation, Sports or Strategy. Any other value matches nothing."
    • changedInput schema / properties / limit / description
      Previous value: -"How many games to return. Defaults to 5."New value: +"Games to return, 1-24. Defaults to 5."
    • changedInput schema / properties / platform / description
      Previous value: -"Only keys for this platform: pc, xbox, playstation or switch."New value: +"Only keys for this platform: pc, xbox, playstation or switch. Omit for all."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "freeToKeep": {
      +      "type": "string"
      +    },
      +    "games": {
      +      "items": {
      +        "properties": {
      +          "genres": {
      +            "items": {
      +              "type": "string"
      +            },
      +            "type": "array"
      +          },
      +          "imageUrl": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "pageUrl": {
      +            "type": "string"
      +          },
      +          "price": {
      +            "type": "string"
      +          },
      +          "releaseYear": {
      +            "type": [
      +              "integer",
      +              "null"
      +            ]
      +          },
      +          "slug": {
      +            "type": "string"
      +          },
      +          "title": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "slug",
      +          "title",
      +          "pageUrl"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "market": {
      +      "type": "string"
      +    },
      +    "ordering": {
      +      "type": "string"
      +    },
      +    "pageUrl": {
      +      "type": "string"
      +    },
      +    "total": {
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "games"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), but the description adds genuinely non-structured context: no prices, no promoted placements, and a pointer to where the time-limited free-to-keep giveaways are claimed instead. It stops short of return-shape or pagination detail, but the output schema covers returns.

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?

Purpose and ordering are front-loaded, then usage routing, then parameters and caveats. Slightly dense as one paragraph and 'free-to-play games, which cost nothing to play' is mildly redundant, but no sentence is filler.

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?

With an output schema present, the description need not explain return values, and it still covers filtering behavior, exclusions (no prices, no promotions), and where related giveaways live. Nothing an agent needs to invoke it correctly 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 baseline is 3, but the description adds combination semantics not present in the schema ('genre and platform ... combine') and clarifies that `total` is the full count and can exceed `limit`, which disambiguates a field the input schema does not define. It leaves `country` entirely to the schema.

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?

States a specific verb and resource ('Return free-to-play games') plus the ordering rule ('most reviewed on Steam first'). It names the siblings it is not (find_games for paid, list_deals for discounts), so an agent can distinguish it without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit selection condition ('when the reader wants something free') and routes two adjacent intents to named alternatives with their own conditions. This is when/when-not/alternatives in one sentence.

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.