Skip to main content
Glama

get_revenue_report

Read-only

Show a revenue report

Revenue comes from the report's revenue_sources: for each source, the amount attribute of its event is added up in US dollars (currency), and negative amounts count as refunds. daily has one entry for each finished UTC day from the first activity in the range, with revenue from every source, paying players (players with revenue from a source with paid_by_player), ARPDAU (revenue divided by active players), payer conversion (paying players divided by active players), ARPPU (revenue from paid_by_player sources divided by paying players), and revenue_by_source, keyed by source label. activity sets what makes a player active on a day: kinds lists which of matches, progression_events, and events count, and event_names limits events to those event names (empty means every event counts). A player is also active on any day they send a revenue source event. cohorts has one entry per first-seen day, newest first, with its new players and the revenue from every source per new player from their first day through day 1, 7, and 30, which is null until that day has finished. averages has the average daily revenue, ARPDAU, payer conversion, and ARPPU over the days (weighted by active and paying player-days), and the revenue per new player over every finished cohort, weighted by cohort size. Without date filters, the report covers the last 90 days.

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": {
      "id": "<id>"
    },
    "name": "get_revenue_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe report ID.
occurred_afterNoOnly include the last N days. Allowed values: 1, 7, 30. Takes precedence over the start of `occurred_between`.
occurred_betweenNoTwo ISO dates (from, to) that limit the cohorts and days to that range. Leave either blank for an open range.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, idempotentHint=false, so the safety profile is covered; the description adds real behavioral context beyond that — the default 90-day window, how revenue is summed in USD with negatives treated as refunds, and that cohort day-1/7/30 values are null until the day finishes. It does not discuss permissions, cost/latency, or error conditions.

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 content is dense and mostly earns its place given there is no output schema, but it is delivered as one undifferentiated paragraph mixing return-value structure with call behavior, with no front-loaded summary of the outputs. A few clauses (the `activity` configuration details) describe state not exposed by any parameter and could be trimmed.

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?

With no output schema, the description legitimately carries the burden of explaining return shape, and it does so thoroughly (daily, cohorts, averages, weighting, null semantics). The remaining gap is operational: it never says where the report `id` originates or what an invalid/unauthorized id does, which matters for a 3-param tool with one required id.

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 three parameters (id, occurred_after, occurred_between) are already documented, and the description only adds the default-window behavior when no date filter is supplied. It introduces concepts like `activity.kinds` and `event_names` that are not present in the input schema at all, which adds conceptual noise rather than clarifying the actual callable parameters.

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?

Opens with a specific verb+resource ('Show a revenue report') and then defines exactly which metrics are returned (daily, cohorts, averages, ARPDAU, ARPPU, payer conversion), which makes the tool's scope unambiguous. It does not name a sibling it differs from (e.g. list_revenue_reports vs. get_archetype_report vs. run_report), so differentiation is left to the reader.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is implied rather than stated: the agent can infer this is the tool for revenue/ARPDAU/cohort analysis, and the default ('Without date filters, the report covers the last 90 days') tells it what happens when filters are omitted. There is no explicit when-to-use vs. when-not, and no guidance on where the required `id` comes from (presumably list_revenue_reports) or when to prefer run_report.

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