Skip to main content
Glama

Revenue

glitchless_revenue
Read-onlyIdempotent

The game's real revenue as RevenueCat or Stripe counts it, for a game connected to either in Glitchless Cloud (Settings → Integrations); a game with both gets both unless source picks one. RevenueCat counts production purchases only (never sandbox, TestFlight or licence-tester ones): revenue and transactions by UTC day, MRR, active subscriptions and trials, installs (its new customers: the first time its SDK starts on a device) next to the new players Glitchless saw, active users a day next to Glitchless's players a day, and, where RevenueCat splits them, revenue by the app version purchases were made on, installs, revenue and purchases by country, and revenue by store (App Store, Google Play) next to the sessions Glitchless measured on iOS and Android. Stripe is the game's own account (a web or PC game's unlock, DLC, supporter packs; a test-mode key says so): revenue by UTC day with refunds, disputes, Stripe's fees and net, new paying customers, revenue by product and by country, and revenue by version and platform for the purchases the game tied to a Glitchless session or player (client_reference_id, or glitchless_session / glitchless_player metadata), with how many players paid. Both give revenue per player Glitchless measured, each day next to its sessions and players, each version next to its players, crash-free sessions and frame-time p95, and what the game's own purchase events (track('purchase', { amount, currency })) add up to: the gap is purchases that never reach Glitchless. Roblox (an experience with an Open Cloud key): Robux earned by UTC day (Robux, not money: it says what they'd be worth through Roblox's Developer Exchange and what that takes), paying users and the share of daily active users who paid, daily active users and new users next to Glitchless's sessions, play time, and D1, D7 and D30 retention by cohort day: the game's retention, since the Roblox SDK is anonymous. Roblox doesn't split revenue by place version. itch.io (a game's page with an itch.io API key): its earnings by UTC day in the currency it has earned most in (others named, never added in), with purchases as its transactions, from the connection's first sync on, since itch.io gives an all-time total only; no split by version or country (its page views, downloads and the browser plays measured there are glitchless_store with show "sales"). Use it for money questions, e.g. whether 1.4.2 earns more per player than 1.4.1, or which DLC gets refunded. Use glitchless_events for purchases by item, level or player.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "glitchless_revenue"
  }
}

Input Schema

NameRequiredDescriptionDefault
envNoOnly include sessions from this environment, e.g. "prod" (what the game passes to init; builds a developer runs usually send "dev")
gameNoThe game, by name or id, when signed in to a workspace (glitchless_list_games lists them); later calls keep it. With a key for one game (gl_sk_…), a call that names another game is refused: sign in to the workspace to reach every game.
hoursNoLook-back window in hours (default 720, 30 days), read as whole UTC days
sourceNoOnly this revenue source (default: every one the game is connected to)
serviceNoGame service name (defaults to the most recently active game)
versionNoOnly this version: its revenue (where RevenueCat splits revenue by version, or Stripe's purchases joined to that version's sessions) over its players. MRR, subscriptions and trials, and Stripe's refunds and fees, stay the whole game's
session_typeNo"user": players only; "tester": people on TestFlight and other test builds only; "synthetic": bots, playtests and store test devices only; "all" or unset: every session. Findings (glitchless_triage, and the overview's) read the production sessions of players unless env or session_type is given

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / source / enum
      Previous value: -[
      -  "revenuecat",
      -  "stripe",
      -  "roblox"
      -]New value: +[
      +  "revenuecat",
      +  "stripe",
      +  "roblox",
      +  "itch"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / game / description
      Previous value: -"The game, by name or id, when signed in to a workspace (glitchless_list_games lists them); later calls keep it. Ignored with a key for one game."New value: +"The game, by name or id, when signed in to a workspace (glitchless_list_games lists them); later calls keep it. With a key for one game (gl_sk_…), a call that names another game is refused: sign in to the workspace to reach every game."
  3. Changed1 schema field changed
    • changedInput schema / properties / source / enum
      Previous value: -[
      -  "revenuecat",
      -  "stripe"
      -]New value: +[
      +  "revenuecat",
      +  "stripe",
      +  "roblox"
      +]
  4. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the description must add semantics — and it does heavily: RevenueCat excludes sandbox, TestFlight and licence-tester purchases; Roblox returns Robux with a DevEx equivalent rather than money and does not split revenue by place version; itch.io figures start at the connection's first sync because the API only gives an all-time total; Stripe test-mode keys are flagged. These are non-obvious data-shape caveats an agent could not infer from the schema.

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 purpose and the routing sentence are correctly front-loaded, but the middle is a dense run-on chain of parentheticals ("installs (its new customers: the first time its SDK starts on a device) next to the new players Glitchless saw") that is hard to scan. Given the tool's breadth much of the content earns its place, but per-source return-value inventories could be tightened or broken into structure.

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 seven parameters, four heterogeneous data sources and no output schema, the description carries the full burden of explaining what comes back — and it does so per source (UTC-day revenue, MRR, cohorts/retention, installs, country/store/version splits, refunds and fees). An agent has enough to choose the tool and predict the response shape.

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 description coverage is 100%, so the schema already documents env, game, hours, source, service, version and session_type in detail — including the source default and the version caveat that MRR/subscriptions/refunds/fees stay whole-game. The description's "unless source picks one" largely restates the schema, so it meets but does not exceed the baseline.

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 opening states a specific resource and scope — "the game's real revenue as RevenueCat or Stripe counts it" — and immediately qualifies the multi-source condition ("a game with both gets both unless source picks one"). It then names the sibling it is not ("Use glitchless_events for purchases by item, level or player"), so an agent can separate it from adjacent tools without opening any 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?

Explicit routing is given both positively ("Use it for money questions, e.g. whether 1.4.2 earns more per player than 1.4.1, or which DLC gets refunded") and negatively (defer purchases-by-item/level/player to glitchless_events; page views and downloads to glitchless_store with show "sales"). The example questions anchor the abstract guidance to concrete intent.

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