Game Stats AI

find_player

Read-only

Look up a player by username (prefix match) and return a summary of their activity: matches played, distinct characters played, most-played character, when they last played, and their 5 most recent matches (match ids for get_match), plus the player attributes stored on them. If several players match, returns the list of candidates so you can ask the user which one.

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": {
      "username": "<username>"
    },
    "name": "find_player"
  }
}

Input Schema

Name	Required	Description	Default
`username`	Yes	The player's username or a prefix of it.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already establish read-only, non-destructive behavior, so the description's job is to add context, and it does: return payload contents, prefix-match semantics, and the ambiguous-match candidate-list behavior that an agent must handle before proceeding. It does not explain why idempotentHint is false or address case sensitivity, but the added behavioral detail is well above the annotation baseline.

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?

A single well-structured sentence that front-loads the action, then the return payload, then the ambiguity case in priority order, with no filler. It runs long and could be split for readability, but nothing is redundant.

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 carries the burden of describing return values, and it does so field by field, including the match-id handoff to get_match. Gaps are minor: no mention of short-prefix result limits or exact-match prioritization when a prefix matches many players.

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?

There is only one parameter at 100% schema coverage, and the schema already states "The player's username or a prefix of it". The description's "(prefix match)" restates that rather than adding syntax, case rules, or minimum-length guidance, so the baseline of 3 applies.

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?

The description opens with a specific verb and resource ("Look up a player by username (prefix match)") and then enumerates exactly what comes back, including the downstream link to get_match. It does not differentiate itself from close siblings such as find_character, list_recent_matches, or get_player_report, so an agent still has to infer the boundary.

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 only implied: the prefix-match framing and the candidate-list fallback describe a disambiguation workflow in which the agent asks the user to pick, which is useful context. However, there is no explicit "use this instead of X" guidance against find_character, get_player_report, or list_recent_matches, which overlap substantially with this tool's outputs.

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?