Skip to main content
Glama

get_source

Read-onlyIdempotent

Get a public game's source from YouGame's own git: clone URL, the live build's commit and version tag, main ref, open crowd test builds, build steps, own-copy rule and how to send work back. Test builds are viewed on the game page; they are not git refs. A compiled web build (Unreal, Unity or Godot built to Wasm) that ships its project source in a source/ folder answers with that source as one ZIP download instead (source.download_url), for the live build and for each open test build that carries its own. Not every game has source: only games open to anyone's test builds, or bound by a licence, are expected to offer it, so "source not public" on a paid or owner-built game is normal, not a fault.

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": {
      "slug": "<slug>"
    },
    "name": "get_source"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe listing slug from /g/<slug>.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses an alternate response shape (a single ZIP at source.download_url for compiled web builds that ship a source/ folder), clarifies that test builds are not git refs, and normalizes the expected 'source not public' outcome. These are exactly the behavioral facts an agent cannot get from structured fields.

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?

The core capability is front-loaded in the first clause and the caveats follow in a logical order (what you get, the ZIP exception, when absence is expected). It is dense and long for a one-parameter tool, but each sentence carries distinct information rather than repetition.

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?

With no output schema, the description carries the full burden of describing return values, and it does so thoroughly, including the conditional ZIP branch and the expected failure message. For a simple read-only lookup, nothing an agent needs to call it correctly or interpret its result is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% for the single required slug parameter, so the schema already explains that it is the listing slug from /g/<slug>. The description adds only indirect meaning by scoping the request to public games, which the schema does not convey, but nothing about slug syntax or format beyond that. Baseline 3 applies.

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 opens with a specific verb and resource ('Get a public game's source from YouGame's own git') and then enumerates exactly what comes back: clone URL, live commit and version tag, main ref, open test builds, build steps, own-copy rule and contribution path. That scope is distinct from any sibling in the list, so an agent can identify the tool 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 Guidelines4/5

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

It gives a clear when-to-expect condition ('only games open to anyone's test builds, or bound by a licence, are expected to offer it') and pre-empts a false-negative reading by saying 'source not public' on paid or owner-built games is normal. It stops short of naming an alternative tool to use instead when source is unavailable.

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