Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

gosugamers_rankings

Fetch GosuGamers Elo team rankings for a specific game and region, optionally filter by team name, and page through results to compare rank, Elo, and rank changes.

Instructions

GosuGamers team rankings. Returns the GosuGamers Elo team ranking for one game, globally or for one ranking region (region_id, taken from the regions list in the response; 0 is Global), with an optional team name prefix q: rank, team id, name, tag, Elo, previous rank and rank change. Paged with page and page_size (up to 100); total_rows reports the size of the ranking. A region_id that the game does not list returns an invalid-parameter error.

Input Schema

NameRequiredDescriptionDefault
qNoTeam name prefix, up to 100 characters
gameYesGame section; one of dota2, counterstrike, lol, valorant, mobile-legends, pubg-mobile, wild-rift, free-fire, battlegrounds-mobile-india
pageNo1-based page; defaults to 1
page_sizeNoPage size, 1 to 100; defaults to 10
region_idNoRanking region id from the regions list of the response; 0 is Global; defaults to 0

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 behavioral disclosure burden. It describes the returned fields, pagination with page/page_size, total_rows, and the invalid-parameter error for a region_id not listed by the game; this is substantial, though it does not explicitly state read-only safety or auth/rate-limit behavior.

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 description is front-loaded and dense with useful information. It moves from purpose to return fields to pagination to error behavior without filler, and every sentence contributes to correct invocation.

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 five-parameter read tool with no output schema and no annotations, the description is nearly complete: it names the returned ranking fields, explains pagination and total_rows, and covers the main region_id error case. Minor gaps remain around response structure details and auth/rate limits, but nothing critical for calling it correctly 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 description coverage is 100%, so the schema already documents all five parameters. The description adds some useful context about the region list and invalid-parameter behavior, but most of its parameter language restates the schema rather than adding new syntax or constraints.

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 states a specific verb and resource: it returns the GosuGamers Elo team ranking for a game, with optional region and team-name filtering. This clearly distinguishes it from GosuGamers team-detail or match endpoints, so an agent can identify it without opening the 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?

It gives clear context: use it for one game's team ranking, globally or for a region, optionally filtered by team prefix. It explains that region_id must come from the regions list and that 0 means Global, but it does not explicitly name alternatives or when not to use this tool.

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