Skip to main content
Glama

check_build

Read-onlyIdempotent

Runs static file and source-reference checks, not the game. Runtime behavior is always not_run; detected SDK references do not prove menu, matchmaking, friends, or ranked behavior. Returns a verdict: ready, risky (warnings), or broken (the game will not start). Pass every file path in the folder (relative to the folder, forward slashes) and the text of index.html; also pass the text of .html/.css/.js files worth scanning (8 MB of text in total). Fix what it reports and run it again until the verdict is ready, then zip the folder's contents for upload at https://yougame.co/upload. For a native build folder (no index.html), pass platform desktop_app: it checks only static files, that there is a program the desktop app can run (Windows: an .exe or Unreal Shipping layout; macOS: a .app; Linux: .x86_64, .x64, .AppImage, .run, .sh, or an ELF file, passing its first bytes) and, when yougame-native.json is beside it (pass its text), that the app accepts it, warning when it has no net (runs offline) or no memoryMb (the limit drops from 8 GB to 4 GB). The game is not run; no index.html is needed.

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": {
      "files": "<files>"
    },
    "name": "check_build"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoListing kind, when known (game, patch or mod). Patch/mod placeholders do not fail the web-stub check.
filesYesEvery file in the build folder.
platformNoOptional listing context. web: plays in the browser. desktop_app: a native build folder without index.html is checked as the native build (program file and yougame-native.json, static only, nothing run); upload it with upload-native.mjs. Forces mobile false. Never ship a web page telling players to download the app.
base_gameNoOptional base-game listing context.
baseRuntimeNoThe listing's base_game.runtime, when set; uses the YG Dolphin/base-game flow.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / baseRuntime
      Added value: +{
      +  "description": "The listing's base_game.runtime, when set; uses the YG Dolphin/base-game flow.",
      +  "type": "object"
      +}
    • addedInput schema / properties / base_game
      Added value: +{
      +  "description": "Optional base-game listing context.",
      +  "properties": {
      +    "runtime": {
      +      "type": "object"
      +    }
      +  },
      +  "type": "object"
      +}
    • addedInput schema / properties / files / items / properties / bytes
      Added value: +{
      +  "description": "Optional first 16 bytes for native executable detection.",
      +  "items": {
      +    "maximum": 255,
      +    "minimum": 0,
      +    "type": "integer"
      +  },
      +  "maxItems": 16,
      +  "type": "array"
      +}
    • changedInput schema / properties / files / items / properties / text / description
      Previous value: -"File contents for index.html and other text files worth scanning (optional)"New value: +"File contents for index.html and other text files worth scanning, and for yougame-native.json in a desktop_app folder (optional)"
    • addedInput schema / properties / kind
      Added value: +{
      +  "description": "Listing kind, when known (game, patch or mod). Patch/mod placeholders do not fail the web-stub check.",
      +  "type": "string"
      +}
    • addedInput schema / properties / platform
      Added value: +{
      +  "description": "Optional listing context. web: plays in the browser. desktop_app: a native build folder without index.html is checked as the native build (program file and yougame-native.json, static only, nothing run); upload it with upload-native.mjs. Forces mobile false. Never ship a web page telling players to download the app.",
      +  "enum": [
      +    "web",
      +    "desktop_app"
      +  ],
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, and the description is consistent with them — it never claims to run or mutate anything. It adds real context beyond annotations: the ready/risky/broken verdict semantics, the 8 MB total text cap, and the yougame-native.json warnings (offline net, memoryMb dropping the limit from 8 GB to 4 GB). The only gap is that the shape of the returned warnings isn't described, though no output schema exists to cover it.

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

Conciseness3/5

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

The web path is front-loaded and efficient, but the native-build section becomes one long run-on sentence with nested parenthetical OS-by-OS file lists ('.x86_64, .x64, .AppImage, .run, .sh, or an ELF file, passing its first bytes'), which is hard to parse. Content is justified, but the structure of the second half costs readability.

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 5-parameter tool with nested objects and no output schema, the description covers what is checked, what the verdict values mean, the size constraints, and both web and native flows. An agent has everything needed to construct a correct call and interpret the result.

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 is 3, but the description adds meaning the schema does not: paths must be relative to the folder with forward slashes, text should include index.html plus .html/.css/.js worth scanning, and there is an 8 MB total text budget. For platform it explains the desktop_app consequences (program-file detection, yougame-native.json, forces mobile false) more fully than the enum description alone.

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 — 'Runs static file and source-reference checks, not the game' — and immediately scopes what it does not do (runtime behavior is always not_run). An agent can distinguish this validation tool from the upload/publish siblings 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit workflow guidance: pass every file path plus index.html text, fix what it reports and re-run until verdict is ready, then zip for upload. It also carves out the alternate path for native build folders (use platform desktop_app, upload with upload-native.mjs) and states that a native folder needs no index.html, so both branches are 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