Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

hltv_team

Read-only

Get a Counter-Strike team profile. Returns one team's public HLTV profile by numeric id: name, country, logo, canonical URL, the team's current HLTV and Valve ranking positions (with regional rank when shown), and the current five-player roster with player ids, nicknames, real names, profile URLs and in-game roles when HLTV publishes them. The trailing slug is cosmetic and optional; HLTV resolves the team by id. Use hltv-rankings to discover team ids.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "hltv_team"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesHLTV numeric team id
slugNoCosmetic team slug; HLTV resolves the team by id

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

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds that the profile is public, that resolution happens by id, and that roles/regional rank are only present "when HLTV publishes them" — a useful disclosure of optional result fields. It does not mention rate limiting or failure behavior for unknown ids, 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 clause, and the id-discovery hint sits at the end where it is actionable. The middle enumeration of return fields is somewhat long and partly redundant with the existing output schema, which is the main efficiency cost.

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 two-parameter lookup with a full output schema and annotations, the definition covers what the tool returns, how to obtain the required id, and which fields may be absent. Nothing an agent needs to invoke it correctly is missing.

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 both parameters are already documented, and the description's note that the slug is "cosmetic and optional" essentially restates the schema text. It adds little semantic meaning beyond the structured fields, so the baseline 3 applies.

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 a Counter-Strike team profile") and enumerates the exact payload: name, country, logo, URL, HLTV/Valve ranking positions, and five-player roster. It also distinguishes itself from the sibling that supplies ids, so an agent can separate it from hltv_rankings or hltv_player without opening a schema.

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?

Explicitly tells the agent to use hltv-rankings to discover team ids, which is real routing guidance for the required parameter. It does not state exclusions (e.g., when to prefer hltv_player or bo3_team for roster data), so it stops short of full when/when-not coverage.

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