Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Wikipedia title suggestions

wikipedia_search_suggest_list
Read-onlyIdempotent

Generate title suggestions for a partial fragment on a Wikipedia edition, returning paginated autocomplete results to help users find the right article title.

Instructions

Get title suggestions for a fragment on a Wikipedia edition. Requires query. 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": {
      "query": "<query>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "wikipedia_search_suggest_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoWikimedia edition code, e.g. `en`, `de`, `ja`, `simple` or `zh-min-nan`. Default: `en`.en
limitNoSuggestions per page, 1 to 100. Default: 10.
queryYesRequired. Title fragment to autocomplete.
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, covering the safety profile. The description adds a genuine behavioral detail beyond that: the result is a list and pagination is cursor-based, which is useful context. However, it does not describe the shape of returned suggestions, so the added value is modest.

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 core action and followed by the requirement and return behavior. Slightly redundant to restate that `query` is required when the schema already marks it required, but otherwise no waste.

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 autocomplete-list tool with no output schema and fully documented parameters, the description covers action, required input, and pagination handling. The only gap is not positioning it against full-text search siblings, which 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 every parameter including lang, limit, query, cursor and the analytics params is already documented in the schema. The description only restates that `query` is required and that `cursor` is for pagination, adding no meaning beyond the schema. 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?

States a specific verb (get title suggestions) and resource (Wikipedia edition, title fragment), which lets an agent distinguish autocomplete from a full-text search tool. It does not name the adjacent sibling (wikipedia_search_list) 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 Guidelines3/5

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

The description gives a light invocation hint ('Requires `query`', 'use cursor when paginated') but never states when this tool is preferable to full-text search or other suggest tools. Usage is implied rather than spelled out with alternatives or exclusions.

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