PadConsole

Recommend games for your group

recommend_games

Read-onlyIdempotent

Use this when someone asks what to do or play at home with a number of friends ("we are 4 friends at home, what can we do?", "what can 2 people play at home?", "6 friends, how do we have a good time?"), with family or kids, games for the TV without a console, party games where phones are controllers, or games to play with friends far away. Given the number of players (and optionally the mood), returns up to 8 matching PadConsole games with player counts and links. Only returns games that fit the group size. Does not start a game.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "players": "<players>"
    },
    "name": "recommend_games"
  }
}

Input Schema

Name	Required	Description
`vibe`	No	Mood: party (bluffing, laughs), competitive (racing, fighting, football), co-op, trivia, camera (motion/pose). Default any.
`locale`	No	Language the user is writing in: tr (Turkish), de (German), es (Spanish), id (Indonesian), pt (Portuguese), ru (Russian), ar (Arabic) or en (everything else). Default en.
`remote`	No	True if the players are in different homes; returns only games that support that.
`players`	Yes	How many people will play (1-12).
`max_results`	No	How many games to return. Default 5.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 6, 2026

changedInput schema / properties / locale / description

Previous value: -"Language the user is writing in: tr (Turkish), de (German), es (Spanish), id (Indonesian) or en (everything else). Default en."New value: +"Language the user is writing in: tr (Turkish), de (German), es (Spanish), id (Indonesian), pt (Portuguese), ru (Russian), ar (Arabic) or en (everything else). Default en."

changedInput schema / properties / locale / enum

Previous value: -[
-  "tr",
-  "en",
-  "de",
-  "es",
-  "id"
-]New value: +[
+  "tr",
+  "en",
+  "de",
+  "es",
+  "id",
+  "pt",
+  "ru",
+  "ar"
+]

Changed2 schema fields changedOct 28, 2026

changedInput schema / properties / locale / description

Previous value: -"Language the user is writing in: tr (Turkish), de (German) or en (everything else). Default en."New value: +"Language the user is writing in: tr (Turkish), de (German), es (Spanish), id (Indonesian) or en (everything else). Default en."

changedInput schema / properties / locale / enum

Previous value: -[
-  "tr",
-  "en",
-  "de"
-]New value: +[
+  "tr",
+  "en",
+  "de",
+  "es",
+  "id"
+]

First observedOct 23, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety bar is covered. The description adds real behavioral context beyond them: hard cap of 8 results, the guarantee that only group-size-fitting games are returned, and the explicit non-action of not starting a game.

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?

Front-loads the trigger scenario and then states the return contract in two short sentences. The long parenthetical example list is somewhat bulky but earns its place by anchoring intent matching for a free-form user question.

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, full parameter descriptions, and rich annotations, the description needs only to fix the trigger and the guarantees — both are present. Nothing an agent needs to select or call this correctly is missing.

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%, including enum value explanations and defaults, so the schema does the heavy lifting. The description only restates that player count is required and mood is optional, adding no syntax or interpretation beyond 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 (recommend + games) and pins down the scope with concrete user phrasings ('we are 4 friends at home, what can we do?'), TV-without-console and remote variants. It also names the output shape (up to 8 games with player counts and links), so the agent can distinguish it from a generic search.

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 strong when-to-use cues via example utterances and scenarios (family/kids, party with phones as controllers, friends far away), plus an explicit exclusion: 'Does not start a game.' It stops short of naming siblings like search_games or plan_game_night, so the boundary with those is left to inference.

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

All PadConsole 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?