Skip to main content
Glama

list_rounds

Read-only

Retrieves one-line summaries for each round in a CS2 match, covering winner, reason, score, buys, bomb, first kill, and tick range.

Instructions

One line per round: winner, reason, score, buys, bomb, first kill, tick range. Use get_round for the kill-by-kill detail.

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": {
      "match_id": "<match_id>"
    },
    "name": "list_rounds"
  }
}

Input Schema

NameRequiredDescriptionDefault
match_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the granularity of the result (one line per round) which is genuinely useful behavioral context, but the field list largely restates what the output schema already provides. No mention of ordering, pagination, or behavior on an invalid match_id.

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 sentences, zero filler, with the result shape front-loaded and the alternative deferred to the end. Every clause carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so the description needn't explain return values, and the tool is simple with a single parameter. However, the sole input parameter is undocumented in both schema and description, which is a real gap for an agent that must supply a valid match_id.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

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

There is one required parameter, match_id, with 0% schema description coverage, and the description never mentions it or its expected format. With low coverage the description is expected to compensate, and it does not. The only implicit signal is that rounds belong to a match.

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 enumerates exactly what a round row contains (winner, reason, score, buys, bomb, first kill, tick range), which makes the resource unambiguous, and it names the sibling get_round as the detail-oriented counterpart. It never states the verb 'list rounds for a match' explicitly, but the field enumeration plus the name leaves little doubt.

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?

It explicitly routes the agent: use this for one-line-per-round summaries, use get_round for kill-by-kill detail. That is a concrete alternative with a selection condition. It stops short of stating prerequisites or when-not to call it at all, so it is not a full 5.

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