Skip to main content
Glama

Foundplay

by io.foundplay
OverviewDiscussionsAdmin

Server Details

Search Foundplay's directory of browser games: AI-made games, mashups and fan ports of classics.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
96.8% over 21 days
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL

TDQS

A4.3/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusion or misselection. The tool's purpose is crystal clear from its name and description.

Naming Consistency5/5

The single tool uses a clear verb_noun pattern (search_games) that is self-explanatory and follows a common convention. No inconsistencies exist because there are no other tools to compare.

Tool Count3/5

A single tool for searching games is borderline thin. While the server's scope is narrow, a directory typically benefits from additional operations like get_game or list_genres, making this feel under-provisioned.

Completeness3/5

The search tool covers discovery and returns rich metadata, but there is no direct way to retrieve a specific game by ID, browse with pagination, or access creator profiles. Notable gaps exist for a game directory surface.

Available Tools

1 tool
search_gamesSearch browser gamesA
Read-onlyIdempotent
Inspect

Searches the free browser games listed on Foundplay, made by independent creators, many of them with AI tools. Matches the query against each game's title, one-line description and genres. Returns each match's title, description, genres, whether it plays on phones, whether people can play it together, play and upvote counts, the creator's X handle when known, and a link to its Foundplay page. Read-only. With no query, returns the most played games.

NameRequiredDescriptionDefault
sortNopopular (most played, the default), trending (last 48 hours) or new.
genreNoOnly games in this genre.
limitNoHow many games to return. Default 8.
phoneNotrue for games with touch controls that play on a phone.
queryNoWords to match, such as 'zombie shooter', 'racing', 'puzzle' or 'cozy farm'.
multiplayerNotrue for games people play together, online or on one screen.

Output Schema

NameRequiredDescription
gamesYes
listsYes
totalYesHow many games matched in all.
browseAllYesEvery game on Foundplay.

TDQS

A4.4/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 the safety profile is covered; the description's 'Read-only' line is redundant with them. It does add real context by disclosing the matching fields and the fallback behavior when no query is supplied, which is beyond what annotations provide.

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?

Purpose and matching semantics are front-loaded, and the sentence structure is clean. The long enumeration of returned fields is largely duplicated by the output schema and could be trimmed, which costs it a point.

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 six optional parameters, full schema coverage, and an existing output schema, the description covers purpose, matching behavior, defaults and the no-query case. Nothing needed to invoke it correctly is missing.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3. The description still adds value by clarifying that the query matches title, one-line description and genres, and by naming the returned fields (phone support, multiplayer, play/upvote counts) that map to the boolean filters, going past the schema's field-level docs.

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 (searches) and resource (free browser games on Foundplay), plus the scope of the corpus and what the query is matched against (title, one-line description, genres). An agent knows exactly what this tool does without opening the schema.

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?

Explains that with no query it returns the most played games, which signals the default usage path, and the schema-level sort/limit options imply refinement. It stops short of explicit when-to-use vs alternatives, though there are no sibling tools to disambiguate against.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • Changedsearch_games1 field changed
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "properties": {
+    "browseAll": {
+      "description": "Every game on Foundplay.",
+      "type": "string"
+    },
+    "games": {
+      "items": {
+        "properties": {
+          "creatorX": {
+            "description": "The creator's X handle, without @.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "genres": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "multiplayer": {
+            "description": "true: people play it together. false: single-player. null: not known.",
+            "type": [
+              "boolean",
+              "null"
+            ]
+          },
+          "phoneFriendly": {
+            "description": "true: plays on phones. false: needs a keyboard. null: not known.",
+            "type": [
+              "boolean",
+              "null"
+            ]
+          },
+          "pitch": {
+            "description": "One line about the game.",
+            "type": "string"
+          },
+          "plays": {
+            "type": "integer"
+          },
+          "title": {
+            "type": "string"
+          },
+          "type": {
+            "type": "string"
+          },
+          "upvotes": {
+            "type": "integer"
+          },
+          "url": {
+            "description": "The game's page on Foundplay, with a Play button.",
+            "type": "string"
+          }
+        },
+        "required": [
+          "title",
+          "pitch",
+          "url",
+          "type",
+          "genres",
+          "phoneFriendly",
+          "multiplayer",
+          "plays",
+          "upvotes",
+          "creatorX"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "lists": {
+      "items": {
+        "properties": {
+          "title": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "title",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "description": "How many games matched in all.",
+      "type": "integer"
+    }
+  },
+  "required": [
+    "total",
+    "games",
+    "lists",
+    "browseAll"
+  ],
+  "type": "object"
+}
  2. 1 tool update
    • Changedsearch_games1 field changed
      • changedInput schema / properties / query / description
        Previous value: -"Words to match, such as 'halo', 'zombie shooter', 'mario kart' or 'cozy'."New value: +"Words to match, such as 'zombie shooter', 'racing', 'puzzle' or 'cozy farm'."
  3. 1 tool update
    • Changedsearch_games1 field changed
      • addedInput schema / properties / multiplayer
        Added value: +{
+  "description": "true for games people play together, online or on one screen.",
+  "type": "boolean"
+}
  4. 1 tool update
    • First observedsearch_games

Related MCP Connectors

Related MCP Servers

  • MCP DOS - Classic DOS Gaming

    basementstudio
    F
    license
    A
    quality
    D
    maintenance
    Provides access to classic DOS games like DOOM, Super Mario, Tetris, and Duke Nukem 3D through js-dos emulation, allowing users to play these legendary games directly from their AI assistant.
    3
    7 npm
    4
    -
  • Cinevva Game Engine by cinevva-engine

    Cinevva Game Engineofficial

    cinevva-engine
    A
    license
    Not graded
    quality
    F
    maintenance
    Turn the AI you already use into a game studio. Describe a game and Claude or Cursor builds it as a real 3D browser game: playable immediately, hosted on its own link, shareable with anyone. No engine, no build step, no code knowledge, nothing to export. Your AI ships the whole thing: it pulls free 3D assets, rigs characters, and playtests its own build until the game works. Free to start.
    MIT
  • debuff by debuffjp

    debuffofficial

    debuffjp
    A
    license
    A
    quality
    B
    maintenance
    Let coding agents play, test and tune your 2D web game. The debuff MCP server attaches to the game you have open (or runs a headless copy) and gives agents live state, explained and source-mapped errors, frame timings, typed params, deterministic replays and rewind, scenario tests and fuzz playtesting. Everything an agent does shows in your dev panel, where you can undo it.
    21
    3
    MIT
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