Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

bo3_match_players

Fetch per-player statistics for a BO3.gg match using its slug, including kills, deaths, assists, headshots, and rating, ordered by team and nickname.

Instructions

BO3.gg per-player match statistics. Returns every player's statistics for one BO3.gg match, ordered by team then nickname: kills, deaths, assists, headshots, first kills and deaths, trades, KAST, rating, ADR, damage, utility and money figures as a numeric stats map, plus the multikill counts (2K to 5K), team and opponent. The match slug comes from bo3-match-history.

Input Schema

NameRequiredDescriptionDefault
slugYesMatch slug from bo3-match-history, for example vitality-vs-natus-vincere-27-10-2026

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4.2/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 largely meets it: it discloses the return ordering ('ordered by team then nickname') and enumerates the fields returned, including that stats come as a numeric `stats` map plus separate multikill counts. It stops short of stating behavior for a missing/invalid slug or empty matches.

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?

It is front-loaded with the one-line purpose, then the return detail, with no filler sentences. The long enumeration of stat fields is somewhat dense but each item informs the caller what is available, so it mostly earns its place.

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?

There is no output schema, so describing the returned fields and ordering is exactly the missing piece, and the description supplies it thoroughly for a one-parameter lookup tool. Nothing material an agent needs to invoke it correctly is absent.

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 coverage is 100% and the single `slug` parameter already documents its source (bo3-match-history) and gives an example. The description repeats that origin rather than adding format or validation detail beyond the schema, so the baseline 3 applies.

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+resource ('per-player match statistics') and explicitly scopes it to 'every player's statistics for one BO3.gg match'. That cleanly separates it from siblings like bo3_match_games (game-level) and bo3_player_stats (player-level aggregates). No ambiguity about what comes back.

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 names the prerequisite source for the required parameter ('The match slug comes from bo3-match-history'), which gives a clear chaining workflow. It does not, however, contrast against alternatives such as bo3_player_stats or bo3_match when a caller might reach for the wrong one, so explicit exclusion guidance is missing.

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