Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

bo3_player_recent_matches

Retrieve up to 30 recent CS2 matches for a player, including opponents, tournaments, map results, and detailed performance stats; filter by opponent or tournament.

Instructions

BO3.gg player recent matches. Returns a CS2 player's newest matches (up to 30) with the opponent, the tournament, the rounds played, each map in order with whether the player's team won it, and the player's own line for the match (rating, kills, deaths, assists, damage, first kills and deaths, trade kills and deaths, headshots, hits, shots, accuracy, money saved and equipment value). Filter by opponent or tournament. Date windows are not supported upstream; the list does not page past 30.

Input Schema

NameRequiredDescriptionDefault
slugYesPlayer slug, for example donk
limitNoNewest matches to return, 1 to 30, default 10
opponentNoOpposing team slug, for example mouz-cs2
tournamentNoTournament slug from bo3-tournaments

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 does disclose the important behavioral traits: a hard 30-item cap, no upstream date filtering, no pagination, and the exact shape of each row down to per-map results and the player's stat line. It says nothing about ordering guarantees beyond 'newest', auth, or rate limits, so not quite a 5.

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?

Purpose is front-loaded in the first sentence, and the long parenthetical field list earns its space because there is no output schema. The limitations sentence is compact and placed after the return shape. Slightly dense but no filler.

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 read-only list tool with no output schema and no annotations, the description covers both the return payload and the hard limits an agent must respect to call it correctly. Remaining gaps are minor, such as whether in-progress or upcoming matches appear and how multiple filters interact.

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, but the description adds real meaning: it clarifies that 'opponent' is a team filter, that 'tournament' is a filter rather than a required scope, and that the 30 cap is a hard upstream ceiling on 'limit'. It does not say whether opponent and tournament combine as AND or OR.

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 gives a specific verb and resource ('Returns a CS2 player's newest matches, up to 30') and enumerates the returned fields, so an agent knows exactly what it gets. It does not explicitly distinguish itself from near-siblings like bo3_player_stats, bo3_match_history or bo3_team_recent_matches, which keeps it from a 5.

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 two supported narrowing filters ('Filter by opponent or tournament') and, crucially, rules out approaches that would otherwise seem natural: no date windows and no paging past 30. It stops short of naming an alternative tool when 30 matches aren't enough or when date-scoped data is needed.

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