Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Search Wikidata

wikipedia_wikidata_search_list
Read-onlyIdempotent

Search Wikidata entities by label, alias, or description to find items, properties, lexemes, forms, or senses; use a cursor to paginate result lists.

Instructions

Search Wikidata entities by label, alias or description. 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_wikidata_search_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoEdition code for labels, aliases and descriptions. Default: `en`.en
typeNoEntity type to search: `item` (default), `property`, `lexeme`, `form` or `sense`.item
limitNoResults per page, 1 to 50. Default: 50. The walk stops at 100 results in total.
queryYesRequired. Text to search for.
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

B3.4/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 description is not carrying the safety burden. It adds the pagination/cursor behavior, which is useful, but omits the 100-result walk cap that affects how an agent should plan a search.

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 purpose, and every clause earns its place. It is on the terse side rather than bloated, with no wasted phrasing.

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 search whose annotations and schema are both rich, the definition covers the essentials. It falls short on routing guidance against the sibling query and entity tools and does not mention the total-result ceiling, though that detail lives in the schema.

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 eight parameters are documented in structured form; baseline is 3. The description restates that query is required and cursor is for pagination but adds no syntax or semantics beyond the schema.

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 and resource: search Wikidata entities by label, alias, or description. That is enough to distinguish it from wikipedia_wikidata_entity_get (lookup by ID), though it never names that sibling explicitly.

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 parenthetical '(use cursor when paginated)' gives a concrete follow-up action, and 'Requires `query`' sets a precondition. However, there is no guidance on when to search entities versus running a SPARQL query (wikipedia_wikidata_query_run) or fetching a known entity directly.

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