Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

bo3_records

Retrieve BO3.gg CS2 standout game and round records, filtered by match, tournament, team, player, record type, and date range with paging.

Instructions

BO3.gg CS2 records with scope and type filters. Returns BO3.gg's CS2 records (standout single-game and single-round performances such as best shots accuracy, clutches, multikills, damage, win streaks) with paging. Scope them to one match, tournament, team or player slug, filter by record_type (for example game_player_headshots), restrict the game day range with from/to, and order newest or oldest. Unscoped requests cover the last six months; each record has its value, unit, side, map, round, player, team and opponents.

Input Schema

NameRequiredDescriptionDefault
toNoLast day, YYYY-MM-DD (UTC); unscoped default is today
fromNoFirst day, YYYY-MM-DD (UTC); unscoped default is six months before to
sortNoOrder by game time; one of newest, oldest; defaults to newest
teamNoTeam slug to scope the records to one team
limitNoPage size, 1 to 100; defaults to 20
matchNoMatch slug to scope the records to one match
offsetNoZero-based offset; defaults to 0
playerNoPlayer slug to scope the records to one player
tournamentNoTournament slug to scope the records to one tournament
record_typeNoRecord type such as game_player_headshots or game_round_player_clutch; the types present are listed in the response

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and clearly frames this as a retrieval tool ('Returns...') with paging, an unscoped six-month default window, and a list of fields present on each record. It does not discuss authorization or rate limits, but it sufficiently discloses the read-only behavior and output 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?

The purpose is front-loaded and the description is appropriately sized for a ten-parameter records tool with no output schema. There is some redundancy, especially 'BO3.gg CS2 records' followed immediately by 'Returns BO3.gg's CS2 records', but the structure remains easy to follow.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity, the rich input schema, and the absence of an output schema, the description is complete enough: it explains the returned record fields, paging, default time window, scoping dimensions, and ordering. An agent has what it needs to invoke the tool correctly.

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 all ten parameters are already documented in the schema. The description reinforces the scoping and filtering model and gives one record_type example, but it adds little syntax or format detail beyond what the schema already provides.

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?

The description gives a specific verb and resource: it returns BO3.gg CS2 records, with examples of standout single-game and single-round performances. The resource is meaningfully distinct from sibling tools like bo3_match or bo3_player_stats, so an agent can identify what this tool is for 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 Guidelines3/5

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

It explains how to use the filters and explicitly states that requests can be scoped by match, tournament, team, or player slug. However, it does not say when to choose this tool over sibling tools such as bo3_player_stats, bo3_tournament_mvps, or bo3_match_players, so usage is only implied.

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