Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

hltv_results

Retrieve finished Counter-Strike 2 match results from HLTV's archive, including teams, scores, winners, events, and formats. Page through results with an offset or filter by event ID.

Instructions

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.

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

NameRequiredDescriptionDefault
eventNoHLTV event id to limit results to one tournament
offsetNoResult offset; 0 is the newest page, 100 is the next page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and does substantial work: page size of 100, reverse chronological ordering, next_offset absent on the last page, total as the full archive count, and the notable edge case that offsets past the end return an empty list rather than an error. It omits authentication and rate-limit behavior, but the paging and boundary semantics are unusually well disclosed for a read-only archive tool.

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-loaded with the core purpose, followed by return shape and then edge-case behavior — a logical progression with no filler sentences. The field enumeration is slightly list-like, but since there is no output schema it earns its space.

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?

With no output schema and no annotations, the description compensates fully: it documents the return fields, page size, ordering, paging contract, terminal-page signal, and out-of-range behavior. An agent could call and page through this tool correctly using the description alone.

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 clarifies offset semantics through the next_offset/total relationship, which adds value beyond the schema, but the `event` filter parameter is never mentioned in the description, leaving that filter's meaning entirely to 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 finished Counter-Strike 2 match results' — and scopes it to HLTV's finished-match archive in reverse chronological order, so the agent knows exactly what data comes back. It does not, however, distinguish itself from the sibling hltv_matches or hltv_event tools, which an agent could plausibly confuse with this archive.

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?

Usage is only implied: 'Pass `offset` to page' tells the agent how to paginate but never says when this tool is preferable to hltv_matches or hltv_event, nor does it mention any prerequisites. The paging instructions are concrete, but there is no explicit when-to-use or when-not-to-use guidance.

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