Skip to main content
Glama
Sign In
Gamealia

Gamealia

Official
by gamealia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Preview in a portal replica

gamealia_preview
Idempotent

Launch a local preview of a built web game inside a replica Gamealia page with mock ads, then get the page and bare game URLs to open. No login or upload; stop it when done.

Instructions

Serves the build (built first unless build:false) inside a local replica of the Gamealia game page (the real portal frame plus mock ads) on 127.0.0.1 and returns the page URL and the bare game URL for the user (or you) to open. No login, nothing is uploaded. It keeps running until stop:true or the MCP server exits; calling it again for the same folder restarts it. For automated checks use gamealia_run_autotest; to play it yourself, gamealia_playtest.

Input Schema

NameRequiredDescriptionDefault
dirYesProject folder (absolute, or relative to the server's working directory)
stopNoStop the preview of this folder instead of starting one
buildNoRun the build command first when the project has one (default true)
titleNoTitle shown on the replica page (default: the build's index.html <title>, else "Preview")

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.18
    • changedInput schema / properties / stop / description
      Previous value: -"Stop the preview of this folder"New value: +"Stop the preview of this folder instead of starting one"
    • addedInput schema / properties / title / description
      Added value: +"Title shown on the replica page (default: the build's index.html <title>, else \"Preview\")"
  2. First observedv0.1.17

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the annotations, it discloses the default build side effect, local 127.0.0.1 hosting, mock ads, absence of login or uploads, and the returned URLs. It also clearly documents the preview's persistent lifecycle, shutdown conditions, and same-folder restart behavior.

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?

The description front-loads the core action and outputs, then covers privacy, lifecycle, and alternatives in three dense but readable sentences. Nearly every clause supplies actionable information, with minimal redundancy.

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?

For a stateful local preview server with an optional build step, the description covers the essential setup, outputs, privacy characteristics, persistence, stopping, restarting, and alternative workflows. Although there is no output schema, the two returned URLs are explicitly identified.

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%, but the description adds operational meaning by connecting dir to same-folder restart behavior and explaining the effects of build:false and stop:true. It does not add anything about title beyond the schema, so this is strong rather than exhaustive parameter supplementation.

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 precisely states that the tool builds if needed, serves the project in a local Gamealia portal replica, and returns both the replica page URL and bare game URL. It distinguishes the tool from gamealia_run_autotest and gamealia_playtest by their respective purposes.

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?

It gives explicit routing guidance: use gamealia_run_autotest for automated checks and gamealia_playtest to play interactively. It also explains when to use build:false and stop:true, and what happens when the tool is called again for the same folder.

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

Deploy Server

Other Tools