Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Wikipedia page languages

wikipedia_page_languages_list
Read-onlyIdempotent

Lists Wikipedia language editions that contain a page for a given title, showing where an article exists across languages. Provide the title and optional starting edition.

Instructions

List the Wikipedia editions that have a page for the title. Requires title. 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": {
      "title": "<title>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "wikipedia_page_languages_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoWikimedia edition code, e.g. `en`, `de`, `ja`, `simple` or `zh-min-nan`. Default: `en`.en
titleYesRequired. Page title on the chosen edition, e.g. `Albert Einstein`, `C++` or `Talk:Barack Obama`. URL-encode it in the path.
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

C2.9/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is fully covered without the description. Beyond restating the purpose, the description adds nothing about the shape of the result (language codes? edition names?), whether the current edition is included, or any ordering or pagination behavior; 'Returns a list' is content-free given there is no output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The definition is short and front-loaded, opening with the purpose before the precondition. However, the third sentence 'Returns a list' conveys almost no information and does not earn its place, and the middle sentence merely repeats the schema's required constraint.

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 simple read-only listing tool with full schema coverage and a complete annotation set, an agent can call this correctly. Still missing is what the returned editions look like and the relationship between the lang parameter and the returned list, which matters because the tool takes a starting edition but returns many. Adequate but with clear gaps.

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, title, context, llm_model and conversation_id is documented in the schema itself. The description only reiterates that title is required, which duplicates the schema rather than adding syntax or format detail. Baseline 3 applies when the schema carries the 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?

The description gives a specific verb and a precisely scoped resource: it lists the Wikipedia editions that contain a page for a given title. That distinguishes it from sibling tools like wikipedia_page_links_list or wikipedia_page_media_list, which deal with different resources on a single page. It does not name a sibling explicitly, so it stops 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only guidance is the precondition 'Requires `title`', which is already enforced by the required list in the schema. There is no statement of when to choose this tool over alternatives such as wikipedia_page_get or wikipedia_search_list, and no exclusions or prerequisites are offered.

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