Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

hltv_valve_ranking

Read-only

Get Get the Valve Counter-Strike team ranking. Returns one Valve (VRS) team-ranking snapshot: the snapshot date, the ranked entries in order (each with rank, the team's id/name/logo, Valve points, the row's region label and the five ranked players with ids and profile URLs), and regions - the region-selector values HLTV publishes for this snapshot. Omit date for the current snapshot; pass a snapshot date (YYYY-MM-DD) to read an older one. Pass region (Europe, Americas or Asia, as listed in regions) to read that regional ranking; a region request reads the base snapshot first to validate the value, so it costs two upstream fetches. An unknown date or region value returns 400; 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_valve_ranking"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoRanking snapshot date (YYYY-MM-DD); omit for the current snapshot
regionNoRegion from the page's own selector: Europe, Americas or Asia

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

A3.7/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing that a region request performs two upstream fetches (validation cost), and that unknown date/region returns 400 while an unpublished date returns 404. Annotations only cover readOnly/openWorld, so this cost and error disclosure is real added value. Slightly short of 5 because the return-shape enumeration duplicates the output schema rather than adding further behavior (caching, freshness, rate limits).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded and the sentence order is logical (purpose, return shape, optional params, error codes). But the long parenthetical enumerating every returned field is wasted length given an output schema exists, and the 'Get Get' duplication signals a lack of editing.

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?

For a zero-required-parameter read with full schema coverage, annotations, and an output schema, the description covers the remaining gaps: snapshot selection, region constraints, and error outcomes. It does not need to explain return values, and its main residual gap is not pointing at the sibling tools it overlaps with.

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 adds meaning beyond the schema: the date format's role in snapshot selection, the fact that `region` values must come from the returned `regions` list, and the two-fetch validation cost of region reads. That is meaningful semantics the schema does not express.

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?

Names a specific verb and resource: fetch the Valve (VRS) Counter-Strike team-ranking snapshot. The scope (Valve/VRS team ranking, not general HLTV rankings) is specific enough that an agent can distinguish it from generic hltv_rankings siblings. Minor deduction for the duplicated 'Get Get' typo and for not naming the closest sibling (hltv_valve_ranking_details) explicitly.

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

Usage Guidelines3/5

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

Gives clear usage modes: omit `date` for current, pass a date for historical, pass `region` for a regional view. However, this is parameter-level guidance rather than tool-selection guidance; it never states when to prefer this tool over `hltv_rankings` or `hltv_valve_ranking_details`, so an agent must infer routing from names alone.

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