Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

bo3_player_stats

Read-only

Returns one statistics view of a BO3.gg player over a day range (default last six months): general (match, game, round, kill, death, assist and damage totals), maps (rating, kills and damage per map) or accuracy (hits, damage and kills by hit group). Provide slug (for example donk), kind and optional from/to days. Use it to evaluate one player; use bo3_match_players for a single match.

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

Input Schema

NameRequiredDescriptionDefault
toNoOptional last day, YYYY-MM-DD. Default: today (UTC).
fromNoOptional first day, YYYY-MM-DD. Default: six months before to.
kindNoOptional view: general (default), maps or accuracy.
slugYesRequired player slug, for example donk.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, openWorldHint), and the description adds the non-obvious behavioral default of a six-month window plus the default 'general' view, which materially changes what data comes back. It does not mention pagination, rate limits, or auth, but the output schema covers the response shape.

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?

Single front-loaded paragraph that leads with the returned resource and scope, then the view enumeration, then the invocation summary and the sibling pointer. The field enumeration is long but each clause carries distinct information; no filler sentences.

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 an output schema present, the description doesn't need to explain return fields, and it covers purpose, view semantics, defaults, and one sibling alternative. Only gap is that the other bo3_player* siblings an agent might confuse this with are not called out.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3; the description earns above that by spelling out what each 'kind' view actually contains (general = match/game/round/kill/death/assist/damage totals; maps = rating/kills/damage per map; accuracy = hits/damage/kills by hit group), which the schema's one-liner 'general (default), maps or accuracy' does not. It also gives a slug example altogether with the date-range defaults.

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?

States a specific verb+resource ('Returns one statistics view of a BO3.gg player') and immediately disambiguates the three view types from siblings like bo3_player_stats vs bo3_player or bo3_team_stats. An agent can tell exactly what data this returns without opening the schema.

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

Usage Guidelines4/5

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

Explicitly says 'Use it to evaluate one player; use bo3_match_players for a single match', giving a clear alternative and selection condition. However, other plausible siblings such as bo3_player, bo3_player_recent_matches, and bo3_player_leaderboard are not addressed, so the routing is incomplete for the crowded bo3_* family.

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

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