Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

gosugamers_player

Retrieve a GosuGamers esports player profile by game and player ID, including rankings, win rate, earnings, social links, and current and previous teams.

Instructions

GosuGamers esports player profile. Returns one GosuGamers player: in-game name, real name, country, GosuGamers Elo rating and world and regional ranking, win/loss/draw record and win rate, streak, career earnings in USD, social links, the current team and previous teams with join and leave dates. A player of a different game than game returns not found.

Input Schema

NameRequiredDescriptionDefault
gameYesGame section; one of dota2, counterstrike, lol, valorant, mobile-legends, pubg-mobile, wild-rift, free-fire, battlegrounds-mobile-india
player_idYesNumeric player id from gosugamers-team (roster[].id)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4.1/5.0
Behavior4/5

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

No annotations are present, so the description carries the burden, and it does disclose the returned fields including rankings, earnings in USD, social links, and team history. It also states the key error condition: a player from another game returns not found. It lacks details on auth, rate limits, or response shape beyond the field list.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is front-loaded with the core purpose and then uses a compact field enumeration to describe the return value. The final sentence adds a useful edge-case constraint without excess wording.

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?

For a single-entity lookup with no output schema and no annotations, the description is complete: it covers what is returned, relevant value types such as USD earnings, and the mismatched-game not-found behavior. The input schema supplies the remaining parameter details.

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%, so the schema already documents both parameters, including the enum and the player_id source from gosugamers-team. The description adds only a small amount of semantics by reinforcing that `game` must match the player's game, but does not elaborate on player_id.

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 uses a specific verb and resource: returns one GosuGamers player profile. It enumerates the returned fields, making clear this is a player lookup rather than a team, match, or tournament endpoint in the gosugamers_* family.

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?

Usage is implied by the player-profile framing and the required game/player_id parameters, but the description never explicitly states when to choose this tool over siblings such as gosugamers_team. The only guidance-like statement is the not-found behavior for a mismatched game.

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