Skip to main content
Glama

What's hot right now

whats_hot
Read-only

Games ranked by a simple, transparent LFG Atlas score: open LFG Atlas posts (people looking for a group now), official updates in the last N days and the game's own live player count from its official source. Each game has why, latest_update (official link), players (source, scope total or steam_only, as_of) and board_url. Player counts are the game's players, never LFG Atlas traffic; always say the source and scope.

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

Input Schema

NameRequiredDescriptionDefault
daysNo
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description's value is in disclosing the ranking recipe (open posts + recent official updates + live player count), the caveat that player counts are the game's own players and never LFG Atlas traffic, and the requirement to cite source and scope. That is meaningful context beyond the annotations; pagination and cost behavior are not covered.

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?

Two sentences, front-loaded with the scoring definition, then the return shape, then the sourcing caveat. Dense but each clause earns its place; the long parenthetical in sentence one slightly slows parsing but adds real information.

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 no output schema, the description steps in to enumerate the return fields (why, latest_update, players with source/scope/as_of, board_url), which is exactly what an agent needs. The remaining gap is parameter behavior — limit and how results are truncated or paged — for an otherwise simple two-parameter tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry parameter meaning. It partially does — 'official updates in the last N days' explains the days window — but says nothing about limit, the defaults (7 and 10), or the bounds (1-30, 1-25). Half the parameter surface remains undocumented.

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?

The description gives a specific verb and resource — games ranked by a composite LFG Atlas score composed of open posts, official updates in the last N days, and live player counts. The composite-ranking framing implicitly separates it from single-signal siblings like latest_updates or get_player_counts, though no sibling is named.

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?

Usage is implied rather than stated: an agent can infer this is the 'what should I look at now' aggregate tool versus the single-signal siblings. There is no explicit when-to-use/when-not guidance and no named alternative, but the closing instruction 'always say the source and scope' does set a downstream usage rule.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources