Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

hltv_events

Read-only

Get the Counter-Strike event calendar. Returns HLTV's public event calendar: ongoing events, featured events, and the month-grouped upcoming list. Each event has its numeric id, canonical url, name, status (ongoing or upcoming), type (for example LAN, Intl. LAN, Online), start/end dates in UTC when published, prize pool and location when the card shows them, and the top participating teams when listed. Use hltv-event with an id from this response for one event's overview.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds useful context beyond them: the data source (HLTV's public calendar), the three groupings returned, the enum-like status values, UTC date normalization, and the fact that prize pool, location, and teams are only present when the card shows them. It does not mention rate limits, pagination, or failure modes, which keeps it below 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.

Conciseness4/5

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

Purpose is front-loaded in the first sentence, followed by return-shape detail and then the routing instruction, so an agent can decide early. The middle enumeration of fields partially duplicates the existing output schema, which is the main bit of unearned length.

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?

For a zero-parameter read tool with annotations and an output schema, the description covers data source, grouping, field availability caveats, and the hand-off to hltv_event. Nothing an agent needs to invoke it correctly or interpret the result is missing.

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?

The tool takes zero parameters, so the baseline is 4; there is no parameter meaning to clarify and nothing in the description misrepresents the input surface. The schema's additionalProperties:false confirms a no-argument call.

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?

The first sentence names a specific verb and resource ('Get the Counter-Strike event calendar') and the second scopes it precisely to HLTV's public calendar with ongoing, featured, and month-grouped upcoming lists. This clearly differentiates it from sibling hltv_event, which the description itself frames as the single-event follow-up.

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?

The final sentence explicitly routes the agent: use hltv-event with an id from this response for one event's overview, which establishes the list-then-detail workflow. It stops short of stating when NOT to use it (e.g., for matches or results, which are sibling tools), so it is clear context rather than full when/when-not guidance.

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