Skip to main content
Glama

get_rivalries

Read-only

Identify CS2 player rivalries by head-to-head kills, nemesis and favourite victim, and duel stats; filter by player, night, date range, or match and sort by duels, diff, or imbalance.

Instructions

Who kills whom across matches. pairs: two players, kills of each on the other (score, the one ahead first), matches they faced each other, opening kills and knife/Zeus kills of each on the other, imbalance (0 even, 1 one-way). players: each player's nemesis ('carrasco', who beats him the most) and favourite victim ('freguês') as 'name (his kills-his deaths)'. No filter = every match; pass player for one player's rivalries. sort: duels (most kills between them) | diff | imbalance.

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": "get_rivalries"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoduels
limitNo
nightNoOne night, YYYY-MM-DD (the evening it started; games after midnight belong to the night before). See list_nights.
sinceNoOnly matches played at or after this ISO 8601 moment.
untilNoOnly matches played before this ISO 8601 moment.
playerNoSteamID or player name.
match_idNo
min_duelsNoLeave out pairs with fewer kills between them (default: 2 per match, 3 to 10).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description goes well beyond them by defining the returned fields, the meaning of `imbalance` (0 even, 1 one-way), and the default min_duels threshold. It stops short of disclosing pagination/limit behavior or result-size costs.

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?

Two tight sentences with backticked field names and parenthetical glosses; the core purpose is front-loaded and every clause carries information about outputs or filters. No boilerplate or repetition.

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 an output schema present, the description need not spell out return values, yet it does so helpfully for a non-obvious duel-stat structure. For an 8-parameter, zero-required aggregation tool it is nearly complete, missing only guidance on the time-window parameters and limit.

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 63%, and the description compensates by explaining all three `sort` values (duels | diff | imbalance), the `player` filter's role, and the default for `min_duels` (2 per match, 3 to 10). It says nothing about `night`, `since`/`until`, `match_id`, or `limit`, leaving a few parameters to the schema alone.

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?

"Who kills whom across matches" is a specific verb+resource statement, and the description immediately distinguishes the two result shapes (`pairs` vs `players`) so an agent knows exactly which question this tool answers. It is clearly different from a raw kill search or a per-player stats tool.

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 a concrete mode switch: "No filter = every match; pass `player` for one player's rivalries," which tells the agent how to select scope. It does not name a sibling alternative for looking at individual kills (e.g. search_kills), so an explicit when-not clause is missing.

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