Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Fandom wiki

fandom_wiki_get
Read-onlyIdempotent

Retrieve a Fandom wiki's metadata, statistics, and enabled features by wiki subdomain or URL to inspect its configuration and available capabilities.

Instructions

Get a Fandom wiki's metadata, statistics and enabled features. Requires wiki.

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

Input Schema

NameRequiredDescriptionDefault
langNoLanguage edition of the wiki, e.g. `de` for fortnite.fandom.com/de. Omit for the main (usually English) edition.
wikiYesFandom wiki subdomain, e.g. `fortnite` for fortnite.fandom.com or `blox-fruits` for blox-fruits.fandom.com. A full wiki host or URL is also accepted.
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=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered. The description adds the useful fact that the response contains wiki-level metadata, statistics, and enabled features, which partially compensates for the absent output schema. It says nothing about error behavior, rate limits, or whether the wiki must exist.

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 with the purpose front-loaded and zero filler; the required-parameter note is placed second. It is efficient, though the terseness is achieved partly by omitting information rather than by tight editing.

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 read-only metadata getter with full schema coverage and rich annotations, the description is minimally adequate, but with no output schema it should say more about the shape of "metadata, statistics and enabled features" and about failure modes such as an unknown subdomain. It leaves the agent guessing what a successful response contains.

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 all five parameters (including lang, context, llm_model, conversation_id) are documented in the schema itself. The description adds no meaning beyond repeating that `wiki` is required, which is the expected 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 uses a specific verb and resource ("Get a Fandom wiki's") and enumerates the payload: metadata, statistics, and enabled features. That distinguishes it from page/content siblings like fandom_page_get or fandom_search_list, though no sibling is named explicitly.

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 "Requires `wiki`," which merely restates the required-parameter constraint already encoded in the schema. There is no statement of when to prefer this over fandom_page_get or the various fandom_*_list tools, and no exclusions or preconditions.

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