Skip to main content
Glama

get_round

Read-only

Retrieves complete detail for a single CS2 round, including every kill, clutch, bomb event, and economy data, so agents can analyze round-level match performance.

Instructions

Full detail of one round: every kill (tick, weapon, headshot, wallbang, smoke, trade…), clutches, bomb events, economy.

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>",
      "round_number": "<round_number>"
    },
    "name": "get_round"
  }
}

Input Schema

NameRequiredDescriptionDefault
match_idYes
round_numberYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare this a read-only, closed-world operation, so the safety profile is covered. The description adds useful substance about the breadth and density of the payload (every kill plus clutches, bomb events, economy) but says nothing about behavior on an invalid round_number or how large the response can get.

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?

One front-loaded sentence with no filler; the colon-plus-list structure quickly conveys scope. Slightly fragmentary with the trailing ellipsis and '…' but nothing is wasted.

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 return-value explanation is not required, and two parameters are simple. Still, the definition leaves an agent without routing guidance versus get_match/list_rounds and without the indexing convention for round_number, which matters for calling it correctly.

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?

Schema description coverage is 0% — both parameters carry only bare titles ('Match Id', 'Round Number'). The description does not compensate: it never clarifies whether round_number is 1-indexed or 0-indexed, whether match_id is an internal ID or a source ID, or how they pair.

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?

Names a clear resource (a single round) and enumerates what 'full detail' means: kills with tick, weapon, headshot, wallbang, smoke, trade flags, plus clutches, bomb events and economy. An agent can distinguish it from get_match or list_rounds by scope, though the description never explicitly contrasts them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance at all: no mention of calling list_rounds first to discover a round_number, no exclusion against get_match for match-level data, and no prerequisites such as needing a valid match_id.

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