Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Wikidata entity

wikipedia_wikidata_entity_get
Read-onlyIdempotent

Retrieve a Wikidata item, property, lexeme, or media entity by ID, or resolve a wiki page title to its linked entity and return selected data.

Instructions

Get a Wikidata item, property, lexeme or media entity, or resolve a wiki title to its entity. Requires id.

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

Input Schema

NameRequiredDescriptionDefault
idYesRequired. Wikidata entity id (`Q937`, `P31`, `L1`, `M925243`), or a page title when `site` is given; `props` is then required.
siteNoWikimedia site id (`enwiki`, `dewiki`, `commonswiki`). When set, `id` is a page title on that site and the entity it links to is returned; `props` is required.
propsNoEntity parts to return, comma- or pipe-separated: `info`, `sitelinks`, `labels`, `descriptions`, `aliases`, `claims`. Required with `site`. Default: all six; without `site` or `languages`, the full entity.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
languagesNoLanguages to return labels, descriptions and aliases in, comma-separated, e.g. `en,de`. Default: every language.
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?

The annotations already declare read-only, idempotent and open-world behavior, so the description's main added value is revealing that lookups can be title-based and that behavior varies by entity type. It says nothing about return shape, entity size, or the fact that a title lookup requires both site and props, which is a meaningful behavioral constraint.

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

Conciseness5/5

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

Two tight sentences with the capability front-loaded and the hard requirement stated second. No filler, no repetition of the title.

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?

With no output schema, the description should hint at what an entity response contains (labels, claims, sitelinks) and how large it can be, but it stops at what can be fetched. For a 7-parameter read tool with full schema coverage this is adequate but leaves a real gap on returns.

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 coverage is 100%, so parameter meaning is already fully documented. The description only restates that `id` is required and does not add anything about how `site`/`props`/`languages` interact beyond what the schema paragraphs already explain.

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?

Names a specific verb and resource ("Get a Wikidata item, property, lexeme or media entity") and adds the alternate mode "resolve a wiki title to its entity". It distinguishes itself from siblings such as wikidata_search_list or wikidata_query_run only implicitly, since no sibling is named.

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 two modes in the description imply when the tool applies (direct id lookup versus title resolution), but there is no explicit guidance on when to prefer wikidata_search_list to find an id first or wikidata_query_run for structured queries. Usage is inferable rather than stated.

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