Skip to main content
Glama

Read the Playgama Bridge SDK docs

get_bridge_sdk_docs
Read-onlyIdempotent

The live Playgama Bridge SDK wiki, for integrating it when an archive answered bridgeSdk: NOT_FOUND or traffic refused with NO_BRIDGE. Without page: the index, one { page, title, required, description? } per page. With page (an id from the index, e.g. "api/storage"): that page’s title, url and markdown, cut to engine’s tabs when the page has tabs and one matches — engineFilter says which tabs existed and which were kept. An unknown page is refused with the list of valid ids. get_game_checklist lists everything the game and its archive must meet, the required Bridge steps included.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage id from the index this tool answers without `page`, e.g. "api/storage" or "api/advertisement/rewarded". A link copied from a wiki page works as-is (with or without `.md`, with or without an anchor — the anchor is ignored; the whole page comes back). Omit to get that index.
engineNoEngine or binding to keep code samples for, matched against the page’s tab titles (e.g. "Plain JS", "Unity", "Construct 3", "GDevelop", "Godot" — matches both Godot 3.x and 4.x —, "GameMaker", "Defold", "Cocos Creator", "Scratch"). Omit to keep every engine’s tab.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations declare read-only/idempotent/no-destructive, and the description goes well beyond them: index shape when `page` is omitted, full page payload (title, url, markdown) when supplied, tab-cutting behavior via `engine`, `engineFilter` reporting, and refusal of unknown ids with valid list. This is rich behavior an agent could not infer from the annotations.

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-loads purpose and then describes the two calling modes compactly, with every clause carrying information. Dense backtick notation and long compound sentences cost a point on readability but not on waste.

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?

No output schema exists, and the description fully compensates by describing both return shapes (index entries with page/title/required/description, and page content with url/markdown/engineFilter). Nothing needed to call or interpret the tool 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 coverage is 100%, so baseline is 3, but the description adds real semantics: the dual mode of `page` (index vs. page fetch) and the tab-filtering side effect of `engine` including what `engineFilter` reports. The schema still carries the enumeration/format details, so it is not a full 5.

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 (read the live Playgama Bridge SDK wiki) plus the precise triggering conditions (archive answered `bridgeSdk: NOT_FOUND`, or traffic refused with `NO_BRIDGE`). An agent can distinguish this docs tool from the game-checklist sibling without opening either schema.

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?

Gives an explicit when-to-use trigger (Bridge SDK integration after a NOT_FOUND / NO_BRIDGE result) and names the alternative, get_game_checklist, along with what that sibling covers. Routing between the two is left unambiguous.

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