Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

bo3_player

Retrieve a BO3.gg player profile by slug to get nickname, team, ratings, prize money, and tournament achievements; optionally filter by game.

Instructions

BO3.gg player profile. Returns a BO3.gg player profile by slug: nickname, name, game, birthday, role, coach flag, country, current team and join date, six-month average rating, career prize money, social links, former names and tournament achievements newest first. Use game to insist on one game; a player of another game is not found.

Input Schema

NameRequiredDescriptionDefault
gameNoGame the player must belong to; one of cs2, valorant, lol, dota2, r6siege, mlbb
slugYesPlayer slug, for example donk

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the whole burden and does disclose meaningful behavior: the full result shape, that achievements are ordered 'newest first', and that a game mismatch yields a not-found result. It stops short of stating read-only/no-side-effects, auth, or rate limits, which are left implicit.

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?

Front-loaded with the verb and resource before the field inventory, and every sentence is functional. The long field enumeration is verbose but justified because no output schema exists.

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?

Without an output schema the description compensates by listing returned fields, and without annotations it explains the game-filter failure mode. A brief note on read-only nature or pagination would round it out, but nothing critical for correct invocation is missing.

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 already 100%, so baseline is 3; the description adds genuinely new meaning by framing `game` as a strict filter with a 'not found' outcome rather than a hint. `slug` semantics are left to the schema example, which is sufficient.

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?

States a specific verb and resource ('Returns a BO3.gg player profile by slug') and enumerates the returned fields, which lets an agent separate it from siblings like bo3_player_stats or bo3_player_recent_matches. The scope (lookup by slug) is unambiguous.

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?

'Use `game` to insist on one game; a player of another game is not found' gives an explicit condition for the optional parameter and its consequence. It does not route the agent between this and the other bo3_player_* siblings, so usage 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.

Deploy Server

Other Tools