Skip to main content
Glama

Wikidata Get Entity

wikidata_get_entity
Read-onlyIdempotent

Get full Wikidata entity by ID (e.g., "Q42" for Douglas Adams, "Q5" for human, "Q1764" for Budapest). Returns labels, descriptions, aliases, claims/statements (properties and values), sitelinks, and the revision the data came from, lastrevid plus the modified timestamp, so live statements can be pinned to a specific edit. Pass "language" (comma/pipe-joined for several) to get labels/descriptions in languages other than English, side by side. For checking several ids at once, use get_entities instead of looping this.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "Q42"
    },
    "name": "wikidata_get_entity"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesWikidata entity ID (e.g., "Q42", "Q937", "P31")
languageNoLanguage code(s) for labels/descriptions/aliases, a single code (e.g. "ka") or a comma/pipe-joined list to compare several at once (e.g. "ka,ru,en"), which returns every requested language's label side by side in one call, the shape needed to decide whether two records in different languages describe the same entity. Default "en". Falls back to "en", then to Wikidata's language-neutral "mul" label, for any requested language the entity has no label in, Q42 (Douglas Adams) has no English label at all, only a "mul" one. When the name came from "mul" it appears under a "mul" key in the labels map, so you can tell where it came from.

Output Schema

NameRequiredDescriptionDefault
idYesWikidata entity ID
typeYesEntity type (e.g., 'item', 'property')
labelYesEnglish label for the entity
claimsYesProperty claims/statements (up to 30 properties, 5 values each)
aliasesYesList of alternative names
modifiedYesUTC timestamp of that revision (ISO 8601)
lastrevidYesRevision id these statements were read at, for pinning the answer to a specific edit
descriptionYesEnglish description of the entity
revision_urlYesPermalink to that exact revision on wikidata.org
wikipedia_enYesEnglish Wikipedia article title if available
sitelinks_countYesNumber of Wikipedia/sister project links

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / language / description
      Previous value: -"Language code(s) for labels/descriptions/aliases — a single code (e.g. \"ka\") or a comma/pipe-joined list to compare several at once (e.g. \"ka,ru,en\"), which returns every requested language's label side by side in one call — the shape needed to decide whether two records in different languages describe the same entity. Default \"en\". Falls back to \"en\", then to Wikidata's language-neutral \"mul\" label, for any requested language the entity has no label in — Q42 (Douglas Adams) has no English label at all, only a \"mul\" one. When the name came from \"mul\" it appears under a \"mul\" key in the labels map, so you can tell where it came from."New value: +"Language code(s) for labels/descriptions/aliases, a single code (e.g. \"ka\") or a comma/pipe-joined list to compare several at once (e.g. \"ka,ru,en\"), which returns every requested language's label side by side in one call, the shape needed to decide whether two records in different languages describe the same entity. Default \"en\". Falls back to \"en\", then to Wikidata's language-neutral \"mul\" label, for any requested language the entity has no label in, Q42 (Douglas Adams) has no English label at all, only a \"mul\" one. When the name came from \"mul\" it appears under a \"mul\" key in the labels map, so you can tell where it came from."
  2. Added

TDQS

A4.6/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly, idempotent, non-destructive, open-world, so the safety profile is covered. The description adds real behavioral context beyond that: lastrevid plus modified timestamp let live statements be pinned to a specific edit, and it explains the language fallback chain to "en" then "mul", including that mul-sourced names appear under a "mul" key. It does not discuss error behavior for nonexistent IDs or response size for very large entities, which keeps it off a 5.

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?

Front-loaded with the core action and examples, then return contents, then the language caveat, then the sibling routing, which is a sensible order. It is dense and slightly repetitive of the schema's own language prose, costing a point but nothing is wasted outright.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With annotations covering safety and an output schema covering response shape, the description supplies the remaining pieces an agent needs: what entity kinds the ID can be (item or property, e.g. P31), revision pinning semantics, and language fallback behavior. Nothing required to select or invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3, but the description adds meaning beyond the schema: why multiple languages matter (deciding whether two records in different languages describe the same entity) and how fallback surfaces in the output. It largely restates the schema's explanation of the language list format, so the added value is real but incremental.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Get full Wikidata entity by ID") and immediately anchors it with concrete ID examples (Q42, Q5, Q1764). It also enumerates the returned data (labels, descriptions, aliases, claims, sitelinks, revision) and names the sibling get_entities as the bulk alternative, so an agent can distinguish it from get_entities and get_wikidata_facts without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly routes single-ID lookups here and multi-ID lookups to get_entities ("instead of looping this"), and gives a concrete use case for the language parameter (comparing records across languages). The when-to-use and when-not-to-use (looping) conditions are both stated rather than inferred.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.