Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Wikipedia user

wikipedia_user_get
Read-onlyIdempotent

Retrieve a Wikipedia user's block status, groups, edit count, registration date, gender and central IDs by username to verify account standing and activity.

Instructions

Get a Wikipedia user's block, groups, edit count, registration date, gender and central ids. Requires name.

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": {
      "name": "<name>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "wikipedia_user_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoWikimedia edition code, e.g. `en`, `de`, `ja`, `simple` or `zh-min-nan`. Default: `en`.en
nameYesRequired. User name on the edition, e.g. `Jimbo Wales` or `ClueBot NG`. A profile URL is not accepted. An IP address has no user record; use the contributions route for its edits.
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

B3.2/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 fully covered by structured data. The description's added value is the list of returned fields, which is meaningful because no output schema exists. It says nothing about rate limits, missing users, or partial/anonymous records, which is why it is not higher.

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 verb and the returned fields. The trailing 'Requires `name`' is redundant with the required array and adds no information, which is the only waste. Otherwise tight and easy to scan.

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?

With no output schema, the enumeration of returned fields is exactly the compensating information an agent needs, and it is present. The remaining complexity gap is the plumbing parameters (context, llm_model, conversation_id), which the schema handles well enough. Adequate for a single-record read tool.

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 lang (edition codes), name (format, max length, IP caveat), context, llm_model and conversation_id in more depth than the description. The description only restates that `name` is required, which is already visible as a required field. Baseline 3 applies since the schema does all the semantic work.

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 uses a specific verb ('Get') plus resource ('a Wikipedia user') and enumerates exactly what comes back: block status, groups, edit count, registration date, gender and central ids. An agent can distinguish this from wikipedia_user_contributions_list because the profile fields are named explicitly. It stops short of naming the sibling it is not, so it lands at 4 rather than 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 when-to-use or when-not-to-use guidance in the description. The one piece of routing advice available — that an IP address has no user record and its edits should go through the contributions tool — lives only in the schema's parameter text, not the description. 'Requires `context`' style guidance is absent entirely.

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