Skip to main content
Glama

hltv_valve_ranking_details

Read-only

Get Get one team's Valve ranking (VRS) point breakdown. Returns the VRS point breakdown HLTV publishes for a lineup: the team card (date, team name and logo, position, points, the row's region label, and the five-player lineup), the five point categories (LAN wins, opponent network, bounty offered, bounty collected, head to head - each with its points), and the five breakdown tables behind those points, each with its id, title, column headers and cell rows. Supply exactly one of team_id (the lineup is resolved from the ranking snapshot for that date, which costs a second fetch) or lineup (five comma-separated HLTV player ids, one fetch). Omit date for the current snapshot. An unknown date or team id returns 400.

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

Input Schema

NameRequiredDescriptionDefault
dateNoRanking snapshot date (YYYY-MM-DD); omit for the current snapshot
lineupNoFive comma-separated HLTV player ids (mutually exclusive with team_id)
team_idNoHLTV team id; its five-player lineup is resolved from the ranking snapshot

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

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

Annotations already cover read-only and open-world behavior, but the description adds genuine operational context the annotations do not: the extra fetch cost of the team_id path versus the single fetch for lineup, and that an unknown date or team id returns 400. The lengthy return-shape narration is somewhat redundant with the existing output schema, which keeps this from 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.

Conciseness3/5

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

Purpose and parameter rules are front-loaded and readable, but the description opens with a duplicated 'Get Get' typo and spends a long clause enumerating return fields that the output schema already documents. The core actionable content could be roughly half as long.

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?

Covers inputs (all three parameters with constraints), outputs (summary of the returned structure), and failure behavior (400 on unknown date or team id). For a read-only detail lookup with a full schema and output schema, 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.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: it explains that team_id is resolved from the ranking snapshot (with a fetch cost), that lineup takes exactly five comma-separated player ids, and that date defaults to the current snapshot. The mutual-exclusivity constraint is the main added semantic.

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 one team's Valve ranking (VRS) point breakdown' — and immediately scopes it to a single lineup's breakdown, which distinguishes it from the broader hltv_valve_ranking list. The follow-up sentence enumerates the exact artifacts returned (team card, categories, tables), leaving no ambiguity about what the tool produces.

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?

Gives concrete invocation guidance: 'Supply exactly one of team_id ... or lineup', 'Omit date for the current snapshot', and the trade-off that team_id costs a second fetch. What it lacks is routing guidance relative to siblings — it never says when to use hltv_valve_ranking instead of this detail tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.