Skip to main content
Glama

Start a Fun Friday game

funfriday_create_session
Destructive

Start a new Fun Friday game session and get back the room code and join link to share with the team. This opens a real room that people can join immediately — confirm with the user before calling it. Works without an account: the room is then limited to the free games, and whoever opens the join link first becomes the host and presses Start, so tell the user to open it themselves before sharing it. With a connected account the room runs on the team's plan, uses one of its games for the week, and its results go on the team leaderboard.

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": {
      "game_type": "<game_type>"
    },
    "name": "funfriday_create_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
game_typeYesWhich game to host. Call funfriday_list_games first if unsure; this is the internal key, not the display name (Imposter is "faker", Colour Clue is "hues_cues").

Output Schema

NameRequiredDescriptionDefault
planYes
join_urlYes
game_nameYes
game_typeYes
hosted_asYes"account" when the room was opened on the signed-in user's team; "guest" when it was opened without an account, so the first person to join becomes the host.
room_codeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / hosted_as
      Added value: +{
      +  "description": "\"account\" when the room was opened on the signed-in user's team; \"guest\" when it was opened without an account, so the first person to join becomes the host.",
      +  "type": "string"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "room_code",
      -  "game_type",
      -  "game_name",
      -  "join_url",
      -  "plan"
      -]New value: +[
      +  "room_code",
      +  "game_type",
      +  "game_name",
      +  "join_url",
      +  "plan",
      +  "hosted_as"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / game_type / enum
      Previous value: -[
      -  "trivia_blitz",
      -  "faker",
      -  "emoji_story",
      -  "two_truths",
      -  "caption_this",
      -  "hot_takes",
      -  "timeline",
      -  "drawing_blind",
      -  "bid_bluff",
      -  "hues_cues",
      -  "majority_rules",
      -  "typing_sprint",
      -  "odd_one_out",
      -  "guess_who",
      -  "ballpark",
      -  "zoomed_in",
      -  "plot_twist",
      -  "top_rank",
      -  "phrase_wheel",
      -  "bluff_trivia",
      -  "code_clues",
      -  "defuse"
      -]New value: +[
      +  "trivia_blitz",
      +  "faker",
      +  "emoji_story",
      +  "two_truths",
      +  "caption_this",
      +  "hot_takes",
      +  "timeline",
      +  "drawing_blind",
      +  "bid_bluff",
      +  "hues_cues",
      +  "majority_rules",
      +  "typing_sprint",
      +  "odd_one_out",
      +  "guess_who",
      +  "ballpark",
      +  "zoomed_in",
      +  "plot_twist",
      +  "top_rank",
      +  "phrase_wheel",
      +  "bluff_trivia",
      +  "code_clues",
      +  "pin_drop",
      +  "defuse"
      +]
  3. Changed1 schema field changed
    • changedInput schema / properties / game_type / enum
      Previous value: -[
      -  "trivia_blitz",
      -  "faker",
      -  "emoji_story",
      -  "two_truths",
      -  "caption_this",
      -  "hot_takes",
      -  "timeline",
      -  "drawing_blind",
      -  "bid_bluff",
      -  "hues_cues",
      -  "majority_rules",
      -  "typing_sprint",
      -  "odd_one_out",
      -  "guess_who",
      -  "ballpark",
      -  "zoomed_in",
      -  "plot_twist",
      -  "top_rank",
      -  "phrase_wheel",
      -  "bluff_trivia",
      -  "code_clues",
      -  "pin_drop",
      -  "defuse",
      -  "black_box",
      -  "knowledge_pursuit"
      -]New value: +[
      +  "trivia_blitz",
      +  "faker",
      +  "emoji_story",
      +  "two_truths",
      +  "caption_this",
      +  "hot_takes",
      +  "timeline",
      +  "drawing_blind",
      +  "bid_bluff",
      +  "hues_cues",
      +  "majority_rules",
      +  "typing_sprint",
      +  "odd_one_out",
      +  "guess_who",
      +  "ballpark",
      +  "zoomed_in",
      +  "plot_twist",
      +  "top_rank",
      +  "phrase_wheel",
      +  "bluff_trivia",
      +  "code_clues",
      +  "defuse"
      +]
  4. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare destructiveHint=true and openWorldHint=false; the description goes much further by explaining that it 'opens a real room that people can join immediately' and by detailing both the account-less path (free games only, first opener becomes host and presses Start) and the account path (team plan, consumes one of the week's games, results land on the team leaderboard). These are exactly the side effects an agent needs before committing to a destructive write.

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-loaded with the action and the returned artifacts, then the confirmation caveat, then the account-dependent behavior. No filler sentences, though the long multi-clause sentences in the account-less explanation are dense enough to slow scanning slightly.

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 covering return values, the description supplies the remaining essentials: confirmation requirement, host-assignment quirk, free-vs-plan game limitation, weekly game consumption, and leaderboard effect. Nothing an agent needs to 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 coverage is 100% and the enum parameter already documents that it is the internal key, not the display name, and points to funfriday_list_games. The description adds no further meaning about game_type, so the baseline of 3 applies.

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 ('Start a new Fun Friday game session') and names the concrete output ('room code and join link to share with the team'). The word 'new' plus the creation framing separates it cleanly from funfriday_get_session and funfriday_list_sessions.

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 explicit preconditions: 'confirm with the user before calling it' and 'tell the user to open it themselves before sharing it.' It does not explicitly name a sibling to prefer in a given situation, so it falls short of full when/when-not/alternatives guidance, but the context for calling it is clear.

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