Read the Playgama game requirements
get_game_checklistEvery numbered rule a game and its build archive must meet to go up on Playgama, read live from the Game Requirements section of the Playgama wiki. Read it together with the Required steps of the Bridge SDK (get_bridge_sdk_docs, page: api) when you start work on a game, before writing code (layout, sound, saving and ads are decided in the first build), and again before every start_archive_upload: check the game and the archive against each item by its number, fix what fails before uploading, and tell the developer which numbers you could not check yourself. If the requirements cannot be read, say so: never report the archive as checked. Without page: { title, url, markdown, pages, requirements, unavailable } — the index; every requirement page as { page, title, required, description? }, all required; the markdown of every page but the platform-specific requirements as { page, title, url, markdown }; and { page, title } of the pages that could not be read right now — tell the developer their rules were not checked. The platform-specific requirements apply to the partner platforms the game is distributed to: read them by page. With page (an id from pages): that page’s title, url and markdown. A Bridge SDK link inside goes to get_bridge_sdk_docs and a guide link to get_game_guides, as their page, as written.
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": "get_game_checklist"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Id of a requirement page from `pages` in the answer without `page`. A link copied from the wiki works as-is (with or without `.md`, with or without an anchor — the anchor is ignored). Omit to get the index with every requirement page. |