Playgama MCP - Publish & Manage HTML5 Games

Get a QA Tool link for a locally served game

get_local_game_qa_tool_link

Read-onlyIdempotent

A link that opens the Playgama QA Tool on a game you serve yourself (e.g. on localhost), to play it in the Bridge SDK harness before uploading. Leave sessionId out for a fresh environment; reuse one to keep saved state.

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": {
      "url": "<url>"
    },
    "name": "get_local_game_qa_tool_link"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	Absolute http(s) URL of the game’s index page, e.g. http://localhost:5503/
`sessionId`	No	Letters, digits, - and _ (up to 64). Default: the current timestamp

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 11, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description adds genuinely new behavior: the tool produces a link rather than performing an action, and sessionId controls whether saved state is preserved. It stops short of saying whether the link expires or assumes the local server must remain reachable.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, no filler, with the core deliverable stated first and the session guidance following. Every clause carries information an agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read-only tool with full schema coverage and annotations, the description covers purpose, preconditions and the one non-obvious parameter behavior. Minor gaps remain around link lifetime and whether the local server must stay running, but nothing blocks correct invocation.

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 the baseline would be 3, but the description adds meaning beyond the schema: omitting sessionId yields a fresh environment, whereas reusing one preserves saved state — a semantic the schema only hints at with 'Default: the current timestamp'.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a concrete deliverable — 'A link that opens the Playgama QA Tool' — and scopes it to 'a game you serve yourself (e.g. on localhost)'. The 'before uploading' clause implicitly distinguishes it from the archive-based sibling get_archive_qa_tool_link, though it never names that sibling directly.

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?

It states the situation clearly: play the game in the Bridge SDK harness before uploading, plus how to choose sessionId for a fresh vs. persisted state. It does not explicitly say 'use get_archive_qa_tool_link instead when the game is already uploaded', so the alternative is left implicit.

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

All Playgama MCP - Publish & Manage HTML5 Games tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?