Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

bo3_team_ranking_dates

Retrieves official BO3.gg ranking dates and valid region labels for a selected game, helping you choose the correct date and region for team rankings.

Instructions

BO3.gg official ranking dates and regions. Returns the days for which Valve published an official ranking for a game (newest first) and the region labels BO3.gg accepts for that game's team rankings. Use it to choose date and region for bo3-team-rankings.

Input Schema

NameRequiredDescriptionDefault
gameNoGame; one of cs2, valorant, lol, dota2, r6siege, mlbb; defaults to cs2

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?

With no annotations, the description carries the burden and does reasonably well: it discloses that results are days Valve published rankings, ordered newest first, and that regions are BO3.gg's accepted labels. It leaves out pagination/limits and the exact region set, which an agent might want to know before relying on the output.

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?

Two tight sentences, front-loaded with what the tool returns and closed with the routing instruction. No filler.

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?

No output schema exists, and the description covers the return contents and ordering, which is the critical part for a parameter-discovery tool. Minor gaps: it doesn't state date formatting or give an example region label, but 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.

Parameters3/5

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

Schema coverage is 100% with a full enum and default documented, so the schema already does the parameter work. The description only implicitly references the `game` parameter ('for a game's team rankings') and adds no format or default guidance beyond the schema, so the baseline 3 applies.

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 resource and output: official BO3.gg ranking dates plus the region labels accepted for a game's team rankings. It is immediately distinguishable from the sibling bo3_team_rankings, which it explicitly serves as a parameter-discovery step.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says 'Use it to choose `date` and `region` for bo3-team-rankings,' naming the alternative and the condition that selects it. An agent knows this is a prerequisite lookup, not the ranking fetch itself.

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