Crawlora MCP

bo3_team_rankings

Read-only

Returns BO3.gg's team ranking for a game, worldwide or for one region, for the latest day or a past date, paged up to 100 per page. Official Valve dates (from bo3_team_ranking_dates) return the official Valve ranking with source valve_official; other dates return BO3.gg's own daily ranking. Provide game, optional region (labels differ per game, listed by bo3_team_ranking_dates), date, page and per_page. Use it for ranking history and regional rankings.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "bo3_team_rankings"
  }
}

Input Schema

Name	Required	Description
`date`	No	Optional ranking day, YYYY-MM-DD. Official Valve dates (bo3_team_ranking_dates) return the official ranking. Default: latest.
`game`	No	Optional game: cs2 (default), valorant, lol, dota2, r6siege or mlbb.
`page`	No	Optional 1-based page, default 1.
`region`	No	Optional region label for the game, listed by bo3_team_ranking_dates. Default: worldwide.
`per_page`	No	Optional page size 1 to 100, default 30.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 28, 2026

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 behavior beyond that: results carry a source field (valve_official vs BO3's daily ranking) depending on the date, and the page cap is 100 — non-obvious traits an agent would otherwise have to discover by calling.

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?

Three tight sentences, with the core purpose front-loaded and the Valve-vs-BO3 nuance immediately after. The "Provide game, optional region, date, page and per_page" clause mildly restates the schema, which is the only wasted motion.

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?

An output schema exists, so return values need not be described. The description covers every input dimension (game defaults, region sourcing, date semantics, paging) plus the dual-source behavior, leaving nothing an agent would need before calling it correctly.

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 the baseline is 3, but the description earns more by tying parameters to cross-tool dependencies: region labels are game-specific and must come from bo3_team_ranking_dates, and date values on official Valve dates change the data source, not just the day. That is meaning the schema alone does not convey.

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 BO3.gg team ranking) plus the precise scope axes: game, worldwide vs one region, latest vs past date, paged up to 100. It also distinguishes itself from the sibling bo3_team_ranking_dates by explaining that Valve official dates yield the Valve ranking while other dates yield BO3's own daily ranking.

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?

Explicitly says to use it "for ranking history and regional rankings" and repeatedly routes the agent to bo3_team_ranking_dates for valid dates and region labels, which is actionable selection guidance. It stops short of stating when not to use it (e.g., versus bo3_valorant_leaderboard), so it falls just short of a 5.

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

All Crawlora MCP tools Inspect

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

Need Help?