Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

bo3_player_stats

Retrieve a BO3.gg player's statistics over a date range, including general totals, map performance, or accuracy by hit group.

Instructions

BO3.gg player statistics. Returns one statistics view of a BO3.gg player over a day range (default: the 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). General views fill stats; the other views fill rows.

Input Schema

NameRequiredDescriptionDefault
toNoLast day, YYYY-MM-DD; defaults to today (UTC)
fromNoFirst day, YYYY-MM-DD; defaults to six months before to
kindNoStatistics view; one of general, maps, accuracy; defaults to general
slugYesPlayer slug, for example donk

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral disclosure burden. It helpfully states that general views populate `stats` and other views populate `rows`, and it documents the default date window, but it does not explicitly state read-only behavior, error handling, rate limits, or pagination.

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?

The description is front-loaded and efficient, with no obvious filler. It is dense but well organized, moving from the core purpose to the view definitions and then to the response-field mapping.

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 four-parameter read-style tool with no output schema and no annotations, the description is reasonably complete: it defines the three views, the default time window, and which output field is populated. It could still say more about response shape or error behavior, but the essential invocation context is present.

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 description coverage is already 100%, so the baseline is 3, but the description adds meaningful semantics for the `kind` enum by explaining what each view contains. It also reinforces the default date range and which response field each view fills.

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 states a specific verb and resource: it returns BO3.gg player statistics over a day range and supports exactly three named views. It is clearly a stats tool rather than a profile or match-history tool, though it does not explicitly distinguish itself from siblings such as bo3_player or bo3_player_recent_matches.

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 implied by the three view options and the default date range, so an agent can infer that this is the tool for aggregate player statistics. However, it does not explicitly say when to choose this over sibling tools like bo3_player or bo3_player_leaderboard, nor does it state exclusions or prerequisites.

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

Deploy Server

Other Tools