Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

gosugamers_rankings

Read-only

Returns the GosuGamers Elo team ranking for one game (dota2, counterstrike, lol, valorant, mobile-legends, pubg-mobile, wild-rift, free-fire, battlegrounds-mobile-india), globally or for one ranking region: rank, team id, name, tag, Elo, previous rank and rank change. region_id comes from the regions list in the response (0 is Global); q filters by team name prefix; page and page_size (up to 100) page through total_rows. Use gosugamers_team with a returned team id for the roster and record.

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>"
    },
    "name": "gosugamers_rankings"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoOptional team name prefix, for example Te.
gameYesRequired game section: dota2, counterstrike, lol, valorant, mobile-legends, pubg-mobile, wild-rift, free-fire or battlegrounds-mobile-india.
pageNoOptional 1-based page, default 1.
page_sizeNoOptional page size 1 to 100, default 10.
region_idNoOptional ranking region id from the regions list of the response; 0 is Global (the default).

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.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds real behavioral context beyond that: the response carries a regions list that feeds region_id, pagination is bounded by total_rows, and page_size caps at 100. Missing only auth/rate-limit or freshness details.

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 core action and scope, then parameters, then the hand-off to gosugamers_team; nearly every clause carries information. The single dense paragraph is slightly run-on but wastes no sentences.

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 five-parameter, read-only ranking tool with a full input schema, complete schema descriptions and an output schema, the definition covers action, scope, parameters, pagination and follow-up tool. Nothing an agent needs to call it correctly 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 100%, so baseline is 3, but the description genuinely adds semantics: region_id's provenance (regions list in the response, 0 = Global), q as a team-name prefix filter, and page/page_size relation to total_rows. This exceeds what the schema alone conveys.

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 the GosuGamers Elo team ranking for one game'), enumerates the supported games and the exact returned fields (rank, team id, name, tag, Elo, previous rank, rank change). It also names the sibling gosugamers_team and explains the difference, so an agent can route without opening either 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?

Explicit chaining guidance: 'Use gosugamers_team with a returned team id for the roster and record', plus 'region_id comes from the regions list in the response (0 is Global)'. It does not state when not to use this tool (e.g., for player rankings or match data), so it falls short of full when/when-not coverage.

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