Skip to main content
Glama

get_match

Read-only

Retrieves a CS2 match overview—status, map, teams, scoreboard stats (K/D/A, ADR, KAST, rating), and top highlights—by match ID, providing a starting point for match analysis.

Instructions

Match overview: status, map, teams, scoreboard (K/D/A, ADR, KAST, rating per player) and the top highlights. Start here.

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

Input Schema

NameRequiredDescriptionDefault
match_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/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 safety and locality are covered by structured data. The description adds the return-content inventory but says nothing about pagination, auth, or size limits on the scoreboard/highlights payload. With annotations carrying the risk profile, this is adequate but not rich.

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?

One front-loaded sentence lists the payload contents, followed by a two-word routing hint. Every clause earns its place and nothing is padded.

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?

An output schema exists, so the return shape need not be explained, and the description still previews the key fields. For a one-parameter read-only tool this is nearly complete; only the provenance of match_id and the drill-down ordering are left implicit.

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?

The single parameter match_id has 0% schema description coverage, so the description is the only place meaning could be added — and it adds none: no indication of the ID format, where to obtain a valid match_id (e.g., list_matches or import_matches), or what happens with an unknown ID. The parameter name is self-describing, which softens but does not fill the gap.

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 the specific resource (a match) and enumerates what the overview contains: status, map, teams, scoreboard metrics (K/D/A, ADR, KAST, rating) and top highlights. That is enough for an agent to tell it apart from get_round (single round detail) or get_player_stats, though it never explicitly contrasts itself with those siblings.

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

Usage Guidelines3/5

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

"Start here" is an implied usage hint that positions this as the entry point before drilling into rounds, highlights, or player stats. There is no explicit when-not or named alternative, so the agent must infer the routing.

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