Skip to main content
Glama

list_nights

Read-only

Retrieve CS2 play nights newest first, with dates, match IDs, maps, player and round counts; use each date as the night key for trophies, rivalries, chat rankings, and player profiles.

Instructions

Nights of play, newest first: date, match ids, maps, how many players and rounds. A night is every match from noon to noon, so games after midnight count for the evening before. Use the date as night in get_trophies / get_rivalries / get_chat_rankings / get_player_profile.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), so the description is free to add the traits that matter: results come back newest-first, and each entry aggregates all matches across a noon-to-noon window, including post-midnight games attributed to the prior evening. That boundary rule is real behavioral context an agent could not infer from the schema.

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?

Three tight sentences: payload and ordering first, then the domain rule that disambiguates the resource, then the handoff instruction. Nothing is repeated and nothing is padding.

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

Completeness5/5

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

An output schema exists, yet the description still summarizes the returned fields, and it covers ordering, aggregation semantics, and downstream use. For a zero-parameter read tool this leaves no meaningful gap for an agent to fill.

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?

The tool takes no parameters, so the baseline is high. The description still adds value by explaining the date format expected by sibling tools that consume the output, which is the closest thing to a parameter contract here.

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?

The description names the resource ('nights of play'), the ordering ('newest first'), and the payload fields (date, match ids, maps, player and round counts), and then defines what a 'night' actually is. That definition is what separates it from list_matches/list_rounds siblings without needing to name them.

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 gives concrete downstream guidance: take the returned date and pass it as `night` to get_trophies, get_rivalries, get_chat_rankings, or get_player_profile. It does not explicitly state when to choose this over list_matches, but the aggregate-vs-raw distinction is strongly implied by the definition of a night.

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