Skip to main content
Glama

Plan a game night

plan_game_night
Read-onlyIdempotent

Use this when someone is planning an evening or event with games: game night, house party, birthday, family night, kids, a couple, an office or team event, Christmas, New Year's Eve or another holiday gathering, or friends in different cities. Builds an ordered PadConsole playlist (warm-up, main games, finale) that fits the group size, the occasion and the time available, with links. 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": "plan_game_night"
  }
}

Input Schema

NameRequiredDescriptionDefault
kidsNoTrue if young children are playing; keeps the plan to games rated age 7 or lower.
localeNoLanguage 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.
remoteNoTrue if some players are in a different home.
minutesNoHow long they want to play. Default 90.
playersYesHow many people will play (1-12).
occasionNofriends, family, kids, couple, birthday, office, remote (players in different homes), solo, or holiday (Christmas, New Year's Eve, Eid or another holiday gathering with mixed ages). Default friends.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • 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"
      +]
    • changedInput schema / properties / occasion / description
      Previous value: -"friends, family, kids, couple, birthday, office, remote (players in different homes) or solo. Default friends."New value: +"friends, family, kids, couple, birthday, office, remote (players in different homes), solo, or holiday (Christmas, New Year's Eve, Eid or another holiday gathering with mixed ages). Default friends."
    • changedInput schema / properties / occasion / enum
      Previous value: -[
      -  "friends",
      -  "family",
      -  "kids",
      -  "couple",
      -  "birthday",
      -  "office",
      -  "remote",
      -  "solo"
      -]New value: +[
      +  "friends",
      +  "family",
      +  "kids",
      +  "couple",
      +  "birthday",
      +  "office",
      +  "remote",
      +  "solo",
      +  "holiday"
      +]
  2. Changed2 schema fields changed
    • 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"
      +]
  3. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds real value by disclosing the shape of the output (ordered warm-up/main/finale playlist with links) and the negative trait that it does not launch a game, but says nothing about selection criteria, failure modes when no plan fits, or limits beyond what the schema carries.

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?

Front-loaded with the trigger condition and only three sentences, but the first sentence is a sprawling scenario list that heavily overlaps the occasion enum values in the schema, repeating structured data. The core value (ordered playlist with links; does not start a game) is buried at the end of that enumeration.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present and full parameter documentation, the definition needs little more, and it does explain the playlist structure and the no-launch boundary. It leaves gaps on what determines game selection and on behavior when constraints conflict (e.g., a 20-minute kids solo plan), which an agent might otherwise assume.

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 schema already documents all six parameters including enums and ranges, making 3 the baseline. The description adds only the causal link that the plan 'fits the group size, the occasion and the time available', which maps players/occasion/minutes to the output but leaves kids, remote, and locale unmentioned in prose.

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 concrete verb and artifact: it builds an ordered PadConsole playlist split into warm-up, main games, and finale, with links, and explicitly excludes starting a game. That artifact description implicitly separates it from search_games and recommend_games, but it never names those siblings, so the differentiation is inferred rather than stated.

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?

Opens with explicit when-to-use framing ('Use this when someone is planning an evening or event with games') and enumerates concrete triggering scenarios including holidays, kids, couples, offices, and distributed friends. The negative boundary 'Does not start a game' removes a likely misroute, but no alternative tool is named for cases this tool does not fit.

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