Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Discord application index

discord_applications_index_list
Read-onlyIdempotent

Lists application IDs from the public Discord app-directory catalogue, with page and cursor inputs for paginated retrieval. Use it to discover Discord app IDs for further lookups.

Instructions

List application ids from the public Discord app-directory 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_applications_index_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, 1 to 50. Each page returns up to 500 application ids; 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=true, openWorldHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is fully covered without the description. The description adds that the result is a bare id list and that cursors are the continuation mechanism, which is useful but thin. It does not disclose rate limits, catalogue freshness, or whether the index covers all public apps.

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 zero preamble. The middle clause 'Optional inputs: `page` and `cursor`' is largely redundant against a 100%-documented schema and is the one sentence that does not fully earn its place.

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 read-only index lister with no output schema, the description covers what the tool returns (ids, paginated) and how to continue. The three meta-parameters (context, llm_model, conversation_id) are thoroughly documented in the schema, so the description need not repeat them. Only the absence of any sibling routing keeps it from a 5.

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%, so the schema already explains page (1-50, up to 500 ids per page) and cursor (from page.nextCursor, same filters only). The description's 'Optional inputs: `page` and `cursor`' merely restates their optionality and adds no format or interaction detail beyond the schema. Baseline 3 applies when the schema carries the parameter burden.

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 application ids from the public Discord app-directory catalogue.' That distinguishes it from siblings such as discord_servers_index_list or discord_games_index_list by naming the exact catalogue, and 'ids' clarifies the narrow output. It stops short of naming the closest alternative (e.g. discord_application_get for full records), so an agent must infer that split.

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: 'List application ids' suggests enumeration/discovery, and 'use cursor when paginated' gives procedural guidance for paging. There is no explicit when-to-use, when-not-to-use, or pointer to a sibling for application details or filtered searches, leaving the agent to infer alternatives from names alone.

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