Skip to main content
Glama

get_trophies

Read-only

Returns CS2 match or night trophies such as MVP, clutch king, entry fragger and best aim, with winners, values and runners-up for each award.

Instructions

Trophies of one match (match_id) or one night (night; default: the most recent night): MVP, clutch king, entry fragger, longest kill streak, longest drought, kills on 10 HP or less, friendly flasher, friendly fire, best and worst aim, died with the knife out, baiter, economist, headshot machine. Each has titles in Portuguese and English, the winner, the value, the numbers behind it and the runners-up; a trophy nobody deserved is left out.

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

Input Schema

NameRequiredDescriptionDefault
nightNoOne night, YYYY-MM-DD (the evening it started; games after midnight belong to the night before). See list_nights.
match_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Read-only and closed-world are already in the annotations, so the description adds the non-obvious semantics instead: the fallback to the latest night and the rule that unelected awards are omitted from the result. It does not discuss cost, ordering or empty-result behavior, keeping it below top marks.

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?

Purpose and selection rules come first, then the award catalog and result shape. The long enumeration of trophy names is bulk but earns its place by telling the agent what questions this tool can answer; the sentence structure is dense but front-loaded.

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 detail field formats, and it still explains what each trophy contains (PT/EN titles, winner, value, supporting numbers, runners-up) and the omission rule. Only edge cases such as a night with no games are left implicit.

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 only 50% because `match_id` has no schema description; the description compensates by explaining that it selects a single match, and reinforces that `night` selects an evening rather than a calendar date. It adds real meaning beyond the schema rather than restating it.

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 resource (trophies) and scope (one match via `match_id` or one night via `night`), and enumerates the exact award types returned. An agent can tell this apart from get_match, get_player_stats or get_round without opening the schema.

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?

Spells out the default selection rule (most recent night) and that either `match_id` or `night` scopes the call, which is the key decision an agent faces. It stops short of naming an alternative tool or stating exclusions, so it is clear context rather than full routing guidance.

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