Skip to main content
Glama

Open Goatcade

open_goatcade
Read-only

Show the Goatcade arcade in the chat: real, free browser games (Rad Rush, atomic-age horde survival; Last Siren, atomic-age survival city builder; Scrap Fury, wasteland combat racer; Nuke Deck, atomic-age roguelike deckbuilder; Solitaire, klondike, spider and freecell; Word Tiles, crossword tile word game vs the computer; Mahjong, mahjong solitaire, every deal winnable; Poker, texas hold'em vs the computer; Bubble Reef, underwater bubble shooter; Brick Blitz, neon brick breaker with bosses; Star Goat, cartoon space shooter with big bosses; Goat Crossing, endless 3d road and river hopper; Geo Quest, learn countries, flags and capitals; Quiz Night, trivia game show, 1,800+ questions; Brain Gym, daily brain workout, 10 mini-games) with a Play button for each. Use this whenever the user wants to play a game, is bored, or asks for Goatcade. Pass game to put one game up front; leave it out to show the whole arcade.

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

Input Schema

NameRequiredDescriptionDefault
gameNoOptional game to feature first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / game / enum
      Previous value: -[
      -  "rad-rush",
      -  "last-siren",
      -  "scrap-fury",
      -  "nuke-deck",
      -  "solitaire",
      -  "word-tiles",
      -  "mahjong",
      -  "poker",
      -  "bubble-reef",
      -  "brick-blitz",
      -  "star-goat",
      -  "goat-crossing"
      -]New value: +[
      +  "rad-rush",
      +  "last-siren",
      +  "scrap-fury",
      +  "nuke-deck",
      +  "solitaire",
      +  "word-tiles",
      +  "mahjong",
      +  "poker",
      +  "bubble-reef",
      +  "brick-blitz",
      +  "star-goat",
      +  "goat-crossing",
      +  "geo-quest",
      +  "quiz-night",
      +  "brain-gym"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / game / enum
      Previous value: -[
      -  "rad-rush",
      -  "last-siren",
      -  "scrap-fury",
      -  "nuke-deck",
      -  "solitaire",
      -  "word-tiles",
      -  "mahjong",
      -  "poker"
      -]New value: +[
      +  "rad-rush",
      +  "last-siren",
      +  "scrap-fury",
      +  "nuke-deck",
      +  "solitaire",
      +  "word-tiles",
      +  "mahjong",
      +  "poker",
      +  "bubble-reef",
      +  "brick-blitz",
      +  "star-goat",
      +  "goat-crossing"
      +]
  3. Changed1 schema field changed
    • changedInput schema / properties / game / enum
      Previous value: -[
      -  "rad-rush",
      -  "last-siren",
      -  "scrap-fury",
      -  "nuke-deck",
      -  "solitaire",
      -  "word-tiles",
      -  "mahjong"
      -]New value: +[
      +  "rad-rush",
      +  "last-siren",
      +  "scrap-fury",
      +  "nuke-deck",
      +  "solitaire",
      +  "word-tiles",
      +  "mahjong",
      +  "poker"
      +]
  4. Changed1 schema field changed
    • changedInput schema / properties / game / enum
      Previous value: -[
      -  "rad-rush",
      -  "last-siren",
      -  "scrap-fury",
      -  "nuke-deck"
      -]New value: +[
      +  "rad-rush",
      +  "last-siren",
      +  "scrap-fury",
      +  "nuke-deck",
      +  "solitaire",
      +  "word-tiles",
      +  "mahjong"
      +]
  5. Changed1 schema field changed
    • changedInput schema / properties / game / enum
      Previous value: -[
      -  "last-siren",
      -  "scrap-fury",
      -  "rad-rush",
      -  "nuke-deck"
      -]New value: +[
      +  "rad-rush",
      +  "last-siren",
      +  "scrap-fury",
      +  "nuke-deck"
      +]
  6. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already confirm this is a safe, read-only operation. The description adds valuable behavioral context by listing the types of games available and noting they are 'real, free browser games' with a 'Play button,' which helps set expectations about the result.

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?

The description is detailed, which is necessary given the scope, but it is generally well-structured. It front-loads the main function and then explains the conditional logic around the 'game' parameter efficiently.

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?

Given the comprehensive list of games and the clear instruction on how to use the single optional parameter, the definition is complete. It tells the agent exactly when and how to call the tool to achieve the user's goal.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the description doesn't need to repeat technical details. Instead, the description defines the *meaning* of the `game` parameter by showing all possible valid enum values and explaining the operational difference between providing one (feature) and leaving it out (show all).

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?

The description explicitly states the tool's function: to 'Show the Goatcade arcade in the chat' and details what this means—present real, free browser games with a play button. This is highly specific.

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?

The description provides explicit instructions for usage: 'Use this whenever the user wants to play a game, is bored, or asks for Goatcade.' It also provides a guide on how to behave when a `game` parameter is present (featured) or absent (show all).

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