Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

hltv_matches

Retrieve live and upcoming Counter-Strike 2 matches from HLTV with teams, events, formats, status, stars, and start times to track the current schedule.

Instructions

Get live and upcoming Counter-Strike 2 matches. Returns HLTV's current live and upcoming Counter-Strike 2 matches, no input needed. Each match has its numeric id, canonical url, scheduled starts_at (UTC; omitted for matches already live), status (live or upcoming), format (bo1/bo3/bo5), stage, star rating stars (0-5), region, LAN flag, both teams with ids and logos, and the event id/name. Use this for the current schedule; use hltv-results for finished matches and hltv-events for tournament calendars. Pinned matches may omit event.name while still carrying event.id.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A4.7/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden and does well: it discloses the returned fields, that starts_at is omitted for live matches, that `status` is live/upcoming, and that pinned matches may omit event.name while keeping event.id. It does not mention pagination, auth, rate limits, or error behavior, which keeps it short of a 5.

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?

Front-loads the purpose in the first sentence, then supplies the return shape compactly, then routing guidance. The field enumeration is dense but justified given there is no output schema.

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 is the sole carrier of both behavior and return shape, and it covers field names, types, edge cases, and alternatives. An agent has everything needed to call it and interpret the result.

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?

Zero parameters, so baseline is 4; the description reinforces this with 'no input needed'. No additional parameter meaning is possible or required.

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 with scope: 'Get live and upcoming Counter-Strike 2 matches' plus 'no input needed'. An agent can distinguish it from hltv_results (finished) and hltv_events (calendars) purely from the description.

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 this for the current schedule' and names two alternatives with the conditions that select them (finished matches, tournament calendars). The only friction is the hyphenated sibling spellings (hltv-results vs hltv_results), which slightly weakens the routing signal.

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