Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

bo3_team_rankings

Fetch current or historical BO3.gg team rankings by game, region, and date, with official Valve rankings and paged roster details.

Instructions

BO3.gg team rankings, current and historical. Returns BO3.gg's team ranking for a game, worldwide or for one region, for the latest day or any past date, paged up to 100 per page. A date that Valve published (listed by bo3-team-ranking-dates) returns the official Valve ranking (source valve_official, official true); other dates return BO3.gg's own daily ranking (internal). Rows carry rank, rank change, points, region, country and the five-player roster with ratings.

Input Schema

NameRequiredDescriptionDefault
dateNoRanking day, YYYY-MM-DD; defaults to the latest
gameNoGame; one of cs2, valorant, lol, dota2, r6siege, mlbb; defaults to cs2
pageNo1-based page; defaults to 1
regionNoRegion label for the game as listed by bo3-team-ranking-dates, for example Europe; omit for worldwide
per_pageNoPage size, 1 to 100; defaults to 30

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden and does well: it discloses the source split (valve_official vs internal), that Valve dates yield official rankings, paging up to 100, and the row contents. It stops short of stating read-only safety or auth/rate-limit details, but the source and pagination disclosures are valuable beyond schema.

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?

Four tight sentences, front-loaded with the core purpose, then scope, then the Valve/internal distinction, then row contents. Dense but every sentence carries information; no wasted filler.

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?

There is no output schema, so the description usefully enumerates the returned fields (rank, rank change, points, region, country, five-player roster with ratings). Combined with pagination and source semantics, an agent has everything needed to call and interpret results.

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 schema already documents all five parameters. The description adds real meaning on top, especially the semantic distinction that a Valve-published date returns an official ranking while other dates return BO3.gg's internal daily ranking, which enriches the `date` parameter beyond its schema text.

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 ('Returns BO3.gg's team ranking') and resource, and enumerates the scoping dimensions (game, region, date). It also names the sibling bo3-team-ranking-dates as the source for Valve-published dates, letting an agent distinguish it from related BO3 tools.

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?

Gives clear context for use: latest or any past date, worldwide or one region. It explicitly routes the agent to bo3-team-ranking-dates to identify Valve dates, which is a genuine when-to-consult hint. No explicit exclusion of alternatives for non-ranking data, but for a ranking tool the guidance is strong.

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