Skip to main content
Glama

list_matches

Read-only

Retrieve analyzed CS2 matches newest first, including map, score, and status. Filter by status and set a limit to review recent results quickly.

Instructions

List analyzed matches (newest first) with map, score and status.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
statusNo

Output Schema

NameRequiredDescriptionDefault
resultYes

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 readOnlyHint=true and openWorldHint=false, so safety is covered. The description usefully discloses newest-first ordering and the three headline fields per match, but says nothing about pagination behavior or what qualifies a match as 'analyzed'.

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 short sentence with the ordering and field summary front-loaded and no filler. Slightly wasted effort listing return fields when an output schema already exists.

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?

For a two-parameter read tool with annotations and an output schema, the definition is serviceable: it establishes scope, order and headline fields. It falls short of complete because the undocumented 'status' filter and the lack of any filtering/pagination guidance leave the agent guessing on the one parameter that carries real semantics.

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%, so the description carries the burden and does not meet it: the 'status' parameter is untyped in schema (anyOf string/null, no enum) and the description never says what values it accepts or whether it filters. 'status' appears only as a returned field, which can actively mislead into thinking it is not a filter. 'limit' is not mentioned at all.

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?

States a specific verb and resource ('List analyzed matches'), adds ordering ('newest first') and returned fields ('map, score and status'). The word 'analyzed' implicitly distinguishes it from list_source_matches, though the contrast is never made explicit.

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, no prerequisites, and no alternatives named. An agent must infer on its own that this is the browsing tool for already-processed matches and what 'analyzed' versus 'source' means.

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