Game Stats AI

get_character_report

Read-only

Show a character 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_character_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.
`threshold`	No	Minimum and maximum bounds for the report threshold filter, as [min, max].
`version_id`	No	Filter to one or more game version IDs. Discover valid IDs from the `filters` in the response.
`event_type_id`	No	Filter to one or more event type 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.2/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, so the safety profile is covered. The description adds no behavioral context of its own — no note that results are paginated, that filter IDs come from the response's `filters`, or what pagination shape to expect, all of which live in the schema rather than the description.

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

Conciseness2/5

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

Three words with no waste, but the brevity is under-specification rather than economy — the single sentence carries no front-loaded scope, constraints, or routing information that would make it useful.

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?

A six-parameter report tool with no output schema needs the description to explain that `id` refers to a report discovered via list_character_reports and that the response includes `filters` and `pagination` objects. None of that is stated, so the description is inadequate for the tool's complexity despite the strong schema.

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 every parameter including the required `id`, the 1-based `page` with pagination semantics, and the filter arrays. Baseline 3 applies; the description contributes nothing beyond what the schema provides.

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?

"Show a character report" restates the tool name with no added specificity: it does not say what a character report contains, what entity scope it covers, or how it differs from the many report siblings (get_character_attribute_report, get_player_report, list_character_reports). An agent knows only that retrieval of some report is involved.

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

Usage Guidelines2/5

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

There is no when-to-use guidance and no mention of alternatives. Nothing indicates that this fetches an existing report by ID while create_report builds one or list_character_reports enumerates IDs, leaving the agent to infer routing from names alone.

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?