Skip to main content
Glama
Sign In

Player Two

by lol.playertwo
OverviewDiscussionsAdmin

Search Player Two's games

search_games
Read-onlyIdempotent

Find games on Player Two (playertwo.lol), a store of games played in the browser: by words (in a game's name, tagline, description, studio, genres, modes and features: every word must match), genre, platform, free or paid, multiplayer, store game or raise. Each game with its slug, name, tagline, studio, genres, modes, price and whether it is free, a sale, a free trial, whether it plays with others, where it plays, players, reviews and its page's address. get_game_facts tells one in full. No key needed.

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": "search_games"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNostore: games out (or coming) in the store; raise: games raising money from players while they are made.
genreNoOnly games with this genre, as Player Two names them (Action, Adventure, Arcade, Arena, Casual, Co-op, Fighting, Horror, Multiplayer, Platformer, Puzzle, Racing, Roguelite, RPG, Shooter, Simulation, Social, Sports, Strategy, Survival, or a game's own).
limitNoHow many, 1 to 50 (20 if left out).
orderNofeatured (Player Two's own order, the default), popular (most players), new (newest first) or playing (most playing now).
priceNofree, paid, or any (the default).
queryNoWords to find, in a game's name, tagline, description, studio, genres, modes or features (every word must match). Left out: every game the filters let through.
offsetNoHow many to skip, for the next page (the answer's next).
platformNoOnly games that play on this.
multiplayerNotrue: only games played with others (by their genres and modes, or their own servers); false: only the others.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered; the description adds genuinely new context by stating 'No key needed' (no auth setup) and by enumerating what each returned game carries (slug, name, tagline, studio, genres, modes, price, sale/free-trial flags, players, reviews, page address) in the absence of an output schema. It stops short of disclosing result caps, rate limits, or that offset drives paging beyond what the schema says.

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

Conciseness3/5

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

Purpose is front-loaded, but the opening sentence sprawls across several stacked parenthetical clauses and is hard to parse in one pass. The return-field list duplicates what the facet list already implies, so some content does not earn its place.

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, 9-parameter search tool with full schema coverage and no output schema, the description supplies the essential missing pieces: what the results contain and that no API key is required. Only the paging contract and the relationship to list_games are left unstated.

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 the enum semantics for kind, genre, order, price and platform are already fully documented. The description largely restates those same facets and the 'every word must match' AND rule that the query schema already states, adding little beyond the baseline.

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: find games on Player Two, a browser-games store, with the searchable facets enumerated (words, genre, platform, price, multiplayer, store vs raise). It also distinguishes itself from get_game_facts, which returns one game in full. The gap is that it never distinguishes itself from the sibling list_games, so an agent must still guess between two listing tools.

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

Usage Guidelines3/5

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

Usage is implied by the facet list — use it to locate games by text or filters — and it explicitly routes to get_game_facts for full detail on a single game. However, there is no statement of when to prefer this over list_games, and no guidance on what to do when a search returns nothing or how to page through results.

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

All Player Two toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources