Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Discord trending games

discord_games_trending_list
Read-onlyIdempotent

Fetch Discord's ten weekly trending games by week and optional category, including official servers, to identify which games are gaining traction.

Instructions

List Discord's ten weekly trending games, by week and optional category, with their official servers. Optional inputs: week, category and include. Returns a list.

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": {
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "discord_games_trending_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
weekNoWeek date, YYYY-MM-DD (Discord publishes on Thursdays). Omit for the latest week.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
includeNo`weeks` adds the published week list (overall and per category). Default: none.
categoryNoTrending category, one of the 18 slugs Discord publishes (e.g. `shooter`, `rpg`, `survival`).
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered elsewhere. The description adds real context beyond that: results are capped at ten, they are published weekly, and each entry carries its official servers. It says nothing about ordering, freshness beyond "weekly", or the pagination/`include` mechanics.

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 short sentences, front-loaded with the resource and scope, with no filler prose. The second sentence is somewhat wasteful because it restates parameters the schema already documents at 100% coverage, though "Returns a list" usefully signals the absence of structured output.

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 six-parameter tool with no output schema, the definition is thin on return shape: it says only "Returns a list" and never indicates what a game entry contains (name, server, position). It is silent on the required `context`, `llm_model` and `conversation_id` plumbing parameters, which the schema covers but which materially affect correct invocation sequencing.

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 100%, including the week date format, the 18 category slugs and the `weeks` include option, so the schema already does the heavy lifting. The description merely names `week`, `category` and `include` without adding format, default or interaction detail, which is the baseline 3 case.

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?

"List Discord's ten weekly trending games, by week and optional category, with their official servers" gives a specific verb, resource, scope (ten, weekly) and even the enrichment (official servers). It does not differentiate from the sibling discord_games_index_list, so an agent cannot tell from the description alone which list tool to pick.

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?

The description offers no when-to-use or when-not-to-use guidance and never references an alternative such as discord_games_index_list or discord_game_get. The closest thing to guidance is "Optional inputs" and the word "optional" before category, which is schema restatement rather than usage selection logic.

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

Deploy Server

Other Tools