Crawlora MCP

bo3_records

Read-only

Returns BO3.gg CS2 records (standout game and round performances: shots accuracy, headshots, clutches, multikills, damage, win streaks) with paging. Scope them with match, tournament, team or player slugs, filter by record_type (for example game_player_headshots), restrict the day range with from/to and order newest or oldest; unscoped requests cover the last six months. Each record has value, unit, side, map, round, player, team and opponents. Use it for highlights; use bo3_player_stats for a player's totals.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "bo3_records"
  }
}

Input Schema

Name	Required	Description
`to`	No	Optional last day, YYYY-MM-DD (UTC). Without a scope the default is today.
`from`	No	Optional first day, YYYY-MM-DD (UTC). Without a scope the default is six months before to.
`sort`	No	Optional order by game time: newest (default) or oldest.
`team`	No	Optional team slug to scope the records to one team.
`limit`	No	Optional page size 1 to 100, default 20.
`match`	No	Optional match slug to scope the records to one match.
`offset`	No	Optional zero-based offset, default 0.
`player`	No	Optional player slug to scope the records to one player.
`tournament`	No	Optional tournament slug to scope the records to one tournament.
`record_type`	No	Optional record type such as game_player_shots_accuracy or game_round_player_clutch; the types present are listed in each response.

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 cover read-only/open-world, so the description's real contribution is the default six-month window for unscoped requests and the paging behavior, both of which materially affect how an agent constructs a call. It does not mention rate limits or result-set size constraints, which keeps it below a 5 for a broad listing tool.

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 purpose, then scoping, then the sibling hand-off — the ordering matches how an agent would need the information. The record shape enumeration (value, unit, side, map, round, player, team, opponents) partly duplicates the output schema and is the one soft spot.

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 needn't explain return values, and with read-only annotations the safety profile is covered. The remaining content — scoping options, date defaults, ordering, and the sibling alternative — is sufficient for correct invocation; only the origin of valid slugs and pagination totals are left implicit.

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 the baseline is 3; the description earns the extra point by explaining a cross-parameter rule the schema cannot express — that from/to default relative to each other and that an unscoped request covers the last six months. It also gives a concrete record_type example, though most other parameter meaning is already in the schema.

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 opens with a specific verb and resource ("Returns BO3.gg CS2 records") and immediately enumerates the record categories (shots accuracy, headshots, clutches, multikills, damage, win streaks), which makes it distinguishable from generic match/player tools. The closing clause explicitly positions it against bo3_player_stats, so an agent can pick between them without opening either 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?

It states the primary use case ("Use it for highlights") and names one alternative with the condition that selects it ("bo3_player_stats for a player's totals"), plus it discloses the implicit default window for unscoped calls. It does not address the other plausible siblings (bo3_player_leaderboard, bo3_match_games), so guidance is clear but not exhaustive.

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.