Game Stats AI

get_progression_report

Read-only

Show a progression report

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_progression_report"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	The report ID.
`page`	No	Page of report rows to return (1-based, defaults to 1). The response `pagination` object reports the current `page`, total row `count`, and total number of `pages`; request pages 1..`pages` to read the full report.
`version_id`	No	Filter to one or more game version IDs. Discover valid IDs from the `filters` in the response.
`occurred_after`	No	Only include data from the last N days. Allowed values: 1, 7, 30.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

C2.1/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered structurally. The description adds zero behavioral context beyond that — no mention of pagination behavior, data freshness, permissions, or what happens with an invalid report ID.

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 single sentence is free of filler, but that is because it carries almost no information rather than because it is tightly written. There is no front-loaded distinction, scope, or routing hint that would let an agent act on it.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a report-retrieval tool with four parameters and no output schema, the description should explain what the report returns and how rows/filters relate. The schema covers mechanics, but the description leaves the agent without enough to decide between this and the many other report tools.

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%, and the parameter descriptions are unusually rich (pagination loop, version ID discovery via `filters`, allowed occurred_after values). The description contributes nothing beyond the schema, but the baseline of 3 applies when the schema fully documents all parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Show a progression report' only restates the tool name get_progression_report, swapping 'get' for 'show'. It gives no indication of what a progression report contains or how it differs from the long list of sibling report tools (get_event_report, get_retention_report, get_player_report, etc.).

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

Usage Guidelines1/5

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

There is no guidance on when to use this tool rather than list_progression_reports, list_progression_types, run_report, or any other report getter in the sibling list. Nothing indicates prerequisites such as needing a report ID obtained from list_progression_reports.

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

All Game Stats AI tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?