Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

hltv_transfers

Read-only

Get Get the latest Counter-Strike player transfers. Returns one page of HLTV's transfer feed, 50 rows per page. Each move carries the player (numeric id, nickname, profile url), the from and to teams (id, name, logo; no_team when HLTV shows "No team"), the roster status label the page shows for that side (for example COACH or BENCH), the move date in UTC, and the page's own description text ("transfers from X to Y", "joins X", "parts ways with X", "is benched on X"). Pass page to page the feed: next_page is the following page number and is absent on the last page.

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

Input Schema

NameRequiredDescriptionDefault
pageNoFeed page; 0 is the newest page

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.8/5.0
Behavior4/5

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

Annotations already declare read-only and open-world access, so the safety profile is covered. The description adds genuinely useful behavior beyond that: a fixed 50-row page size, UTC dates, `no_team` sentinel handling, and the pagination termination rule (`next_page` absent on the last page). It does not mention rate limits or freshness/caching, which keeps it out of 5 territory.

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?

The core purpose and page size are front-loaded, and sentences are dense but purposeful. It is somewhat over-invested in enumerating return-field shapes that the output schema already covers, and it opens with a duplicated word ('Get Get'), a small blemish.

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?

With a read-only annotation set and an output schema present, the definition covers everything needed to call it correctly, including the pagination edge case. The main redundancy is restating the response field structure, which the output schema already supplies.

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% and the schema already says page 0 is the newest page. The description still adds meaning the schema cannot express: `next_page` in the response is the number to pass next, and its absence signals the end of the feed, which materially changes how an agent drives pagination.

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?

The description names a concrete verb and resource ('Get the latest Counter-Strike player transfers') plus the source ('HLTV's transfer feed'), which implicitly separates it from the other provider-specific transfer siblings. It does not explicitly route the agent away from those siblings, so it stops short of a 5.

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 implied rather than stated: the tool fetches the newest transfers, and the description explains how to page through the feed via `page`/`next_page`. There is no explicit when-to-use vs. when-not guidance (e.g., when to choose this over another transfers source, or whether historical seasons are covered).

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