Crawlora MCP

hltv_results

Read-only

Get finished Counter-Strike 2 match results. Returns one page of HLTV's finished-match archive, 100 results per page in reverse chronological order. Each result has the match id, canonical url, group date (YYYY-MM-DD), both teams with logos, score as [team1, team2], winner (1 or 2), event name, format, and star rating. Pass offset to page: next_offset in the response is the value for the following page and is absent on the last page; total is the archive's full result count. Offsets past the end return an empty results list rather than an error; the optional event filter restricts the archive to one event id, team restricts it to one team's results, map restricts it to one map slug (validated against the page's own map list) and stars keeps results at or above the given star rating (1-5); the response also carries the maps discovery list.

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_results"
  }
}

Input Schema

Name	Required	Description
`map`	No	Map slug to limit results to matches where it was played; see the response `maps` list
`team`	No	HLTV team id to limit results to one team
`event`	No	HLTV event id to limit results to one tournament
`stars`	No	Minimum star rating; one of 1, 2, 3, 4, 5. Documented values: 1, 2, 3, 4, 5.
`offset`	No	Result offset; 0 is the newest page, 100 is the next page

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.

AddedNov 11, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only mark the tool read-only and open-world; the description adds page size, reverse chronological order, next_offset absence on the last page, total count, and that out-of-range offsets return an empty list rather than an error. These are meaningful behavioral details beyond the annotations and are consistent with readOnlyHint.

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?

Front-loads purpose and keeps pagination and filter guidance in a compact sequence. However, it enumerates many output fields despite having an output schema, so some wording is redundant for the description's selection job.

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?

Covers purpose, pagination edge cases, filter behavior, and response navigation for a five-parameter archive tool. With annotations and an output schema present, nothing essential is missing for correct invocation.

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 paging semantics such as next_offset, total, and empty results past the end. It also clarifies map validation against the response maps list and that stars acts as a minimum rating, though event and team add little beyond the schema.

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: 'Get finished Counter-Strike 2 match results,' scoped to HLTV's finished-match archive. The word 'finished' and the archive framing distinguish it from live/upcoming match tools and single-match 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?

Explains how to page and filter via offset, event, team, map, and stars, including the empty-results behavior past the end. It never names alternative sibling tools or states when to choose this over hltv_matches or hltv_match, so exclusions and alternatives are absent.

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.