Crawlora MCP

bo3_player

Read-only

Returns a BO3.gg player profile by slug: nickname, name, game, birthday, role, coach flag, country, current team and join date, six-month average rating, career prize money, social links, former names and tournament achievements newest first. Provide slug (for example donk) and optionally game to assert it. Use it to identify a player; use bo3_player_stats for statistics and bo3_records for standout performances.

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": {
      "slug": "<slug>"
    },
    "name": "bo3_player"
  }
}

Input Schema

Name	Required	Description	Default
`game`	No	Optional game to assert: cs2, valorant, lol, dota2, r6siege or mlbb; a player of another game is not found.
`slug`	Yes	Required player slug, for example donk.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 28, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds real context on top: the exact field set returned, that achievements are ordered 'newest first', and that game acts as an assertion. It stops short of describing pagination or limits, but this is a single-record lookup so that gap is minor.

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?

Three sentences, front-loaded with the return payload before the usage guidance, and every sentence carries information. The field enumeration is long but earns its place by letting an agent judge coverage before calling.

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?

For a two-parameter, annotated lookup with an output schema present, the description covers identity, scope, and routing. The field list overlaps with what the output schema likely already declares, but it usefully signals the breadth of the profile so the agent knows this single call avoids extra round trips.

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 coverage is 100% and both parameters are already documented in the schema with an example and an enumerated game list. The description repeats 'slug (for example donk)' and 'optionally game to assert it' without adding syntax or semantics beyond the structured fields, so baseline 3 applies.

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?

Opens with a specific verb and resource ('Returns a BO3.gg player profile by slug') and enumerates exactly what the payload contains, from nickname through tournament achievements. It also names the sibling tools it is not, so an agent can distinguish it from bo3_player_stats and bo3_records without opening a 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?

Explicitly states the selection rule ('Use it to identify a player') and routes the agent to the two alternatives with the condition that selects each: bo3_player_stats for statistics, bo3_records for standout performances. It also says the game param is optional and asserts identity rather than filtering.

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

All Crawlora MCP 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?