Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List random Wikipedia pages

wikipedia_random_list
Read-onlyIdempotent

Fetches a list of random Wikipedia pages from a chosen language edition and namespace, with an adjustable result limit, for sampling or discovery tasks.

Instructions

List random pages in a Wikipedia edition and namespace. Optional inputs: lang, namespace and limit. 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": "wikipedia_random_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoWikimedia edition code, e.g. `en`, `de`, `ja`, `simple` or `zh-min-nan`. Default: `en`.en
limitNoPages to return, 1 to 500. Default: 10.
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.
namespaceNoNamespace id, e.g. `0` for articles or `14` for categories.
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.1/5.0
Behavior2/5

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

Annotations already declare readOnly, non-destructive, openWorld and even idempotent, so the safety profile is carried by structured data. The description adds essentially nothing beyond those: it does not say that results are non-deterministic (a fresh random set per call), gives no indication of page/item shape beyond "a list," and mentions no rate limits or edition coverage. The non-determinism point matters because the idempotentHint annotation arguably misleads for a random sampler, and the description does not correct it.

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 clauses with the core scope front-loaded and no filler. The trailing "Returns a list" is near-redundant with "List" and adds little, keeping it just below top marks.

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 sampling tool with fully documented schema and rich annotations, the description covers the essentials (what is listed, in which edition/namespace, how many). The main omission is the behavior an agent most needs to know — that each invocation returns a different random set and that results overlap is expected.

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 every parameter (including lang, namespace, limit bounds, and the required context/llm_model/conversation_id preamble) is already documented. The description merely echoes three of the six parameters by name without adding format or semantics, 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?

The description states a specific verb and resource — "List random pages in a Wikipedia edition and namespace" — and the word "random" distinguishes it from the deterministic list/search siblings such as wikipedia_search_list or wikipedia_category_members_list. It does not explicitly name an alternative, so it stops short of 5.

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?

There is no statement of when to use this tool versus a search or category listing, and no exclusions or prerequisites. The only guidance-like content ("Optional inputs: lang, namespace and limit") just restates schema optionality rather than selection criteria.

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