Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

hltv_rankings

Fetch an HLTV Counter-Strike world team ranking snapshot with ranks, points, weekly changes, and top players, or pass a date to read an older published ranking.

Instructions

Get the HLTV world team ranking. Returns one HLTV Counter-Strike world-ranking snapshot: the snapshot date and every ranked team in order, each with rank, team id/name/logo, HLTV points, the week-over-week change (+1, -2, new, or - for unchanged), and the five ranked players with their ids and profile URLs. Omit date for the current ranking; pass a snapshot date (YYYY-MM-DD, typically a Monday) to read an older ranking. A date with no published snapshot returns 404.

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": "hltv_rankings"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoRanking snapshot date (YYYY-MM-DD); omit for the current ranking
countryNoCountry or region from the ranking page's own region selector

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A4/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden and does a fair job: it discloses the response shape (snapshot date, ordered teams, rank/points/change/players), notes the 404 on unpublished dates, and spells out the `change` encoding ('+1', '-2', 'new', '-'). It says nothing about rate limits, caching, or auth, which leaves some behavioral ground uncovered.

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?

Three tight sentences in a deliberate order: purpose, then return contents, then parameter guidance and failure mode. The enumeration of return fields is justified because there is no output schema; nothing is redundant.

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?

With no annotations and no output schema, the description properly compensates by describing the returned fields and the date/404 semantics. The one gap is that `country` is dropped entirely, so an agent cannot tell whether this tool is world-only or supports regional rankings.

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%, so baseline is 3. The description adds real meaning for `date` (format, 'typically a Monday', 404 behavior), but it never mentions `country` at all, leaving an unexplained tension between 'world team ranking' in the description and a region selector parameter in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Get the HLTV world team ranking'. The resource ('world team ranking') is distinct enough from the sibling hltv_team/hltv_matches tools that an agent can tell what it returns, but the description never explicitly contrasts itself against those siblings.

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 concrete when-to guidance for the one meaningful choice: 'Omit `date` for the current ranking; pass a snapshot date ... to read an older ranking', plus the failure condition 'a date with no published snapshot returns 404'. It stops short of naming an alternative tool for related needs (e.g. team details), so it is clear context without exclusions.

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