Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Discord game index

discord_games_index_list
Read-onlyIdempotent

Retrieve Discord game IDs and slugs from the public catalogue, using optional page and cursor inputs to paginate and build or refresh game indexes.

Instructions

List game ids and slugs from the public Discord game catalogue. Optional inputs: page and cursor. Returns a list (use cursor when paginated).

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, 1 to 60. Each page returns up to 500 ids and slugs; omit for the first page and pass `page.nextCursor` to continue.
cursorNoCursor from `page.nextCursor` of the previous response. It only works with the same filters.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
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

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds that the catalogue is public and that results are paginated with a cursor, but says nothing about rate limits, ordering, or result size beyond 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the core purpose and followed by the optional inputs and pagination hint. There is minor redundancy between 'Optional inputs: page and cursor' and 'use cursor when paginated', but nothing is wasted.

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?

For a simple read-only list tool with a fully documented schema and annotations, the description covers purpose, scope (public catalogue), and pagination adequately. The absence of return-shape detail is acceptable since the description states it returns a list of ids and slugs.

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%, and the schema documents page, cursor, context, llm_model, and conversation_id in detail. The description merely repeats that page and cursor are optional inputs, adding no meaning beyond the schema, so the baseline 3 applies.

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 states a specific verb and resource ('List game ids and slugs from the public Discord game catalogue'), which clearly identifies the operation and its scope. It does not explicitly distinguish itself from siblings like discord_games_trending_list or discord_game_get, so it falls short of a 5.

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?

It gives pagination guidance ('use cursor when paginated') and notes page/cursor are optional, which implies usage context. However, it never states when to choose this over discord_games_trending_list or discord_game_get, and offers no exclusions or prerequisites.

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