Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

gosugamers_player

Read-only

Returns one GosuGamers esports player: in-game and real name, country, Elo rating with world and regional ranking, win/loss/draw record and win rate, streak, career earnings in USD, socials, current team and previous teams with join and leave dates. Requires game and player_id (roster[].id from gosugamers_team); a player of another game returns not found.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "game": "<game>",
      "player_id": "<player_id>"
    },
    "name": "gosugamers_player"
  }
}

Input Schema

NameRequiredDescriptionDefault
gameYesRequired game section: dota2, counterstrike, lol, valorant, mobile-legends, pubg-mobile, wild-rift, free-fire or battlegrounds-mobile-india.
player_idYesRequired numeric player id (roster[].id) from gosugamers_team.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds real value beyond that: the not-found-on-mismatched-game behavior and the complete field payload. It doesn't discuss rate limits or pagination, but for a single-record read this is close to full disclosure.

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?

Two sentences, front-loaded with the return payload, then requirements and the negative case. Efficient; the field enumeration is long but earns its place by signaling what the agent will get.

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 annotations and an output schema present, the description needn't explain returns, yet it still conveys inputs, provenance of the id, and failure behavior. 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.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and both parameters are documented there. The description reinforces player_id as roster[].id from gosugamers_team, matching the schema, so it adds little beyond it. Baseline 3 for high-coverage 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?

States a specific verb and resource (returns one GosuGamers esports player) and enumerates the exact data fields returned. An agent can distinguish this from team/match/tournament siblings without opening any 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?

Clearly gives the required inputs, the provenance of player_id (roster[].id from gosugamers_team), and the cross-game failure behavior ('a player of another game returns not found'). This is strong context, though it doesn't name an explicit alternative tool condition (none exists for players).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP toolsInspect
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.

Resources