Skip to main content
Glama

Wikidata

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Get Wikidata Facts

get_wikidata_facts
Read-onlyIdempotent

Structured facts about a Wikidata entity in HUMAN-READABLE form — property names and values resolved to labels, not raw P/Q codes. PREFER OVER get_entity for "what is X's ", "facts about X", "X's date of birth / capital / population". E.g. Q42 (Douglas Adams) -> {"date of birth":["1952-03-11..."],"occupation":["writer",...],"place of birth":["Cambridge"]}. Also returns lastrevid and modified, the revision these statements were read at, for questions asking about an item's state after its latest edit. Pass "language" (comma/pipe-joined for several) for facts and labels in languages other than English. Pass a Q-id from search_entities.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesWikidata entity Q-id (e.g. "Q42"). Find it with search_entities.
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.

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\" for any requested language the entity has no label in."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. Changed2 schema fields changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "id": "Q42"
-  },
-  {
-    "id": "Q1764"
-  }
-]New value: +[
+  {
+    "id": "Q42"
+  },
+  {
+    "id": "Q162887",
+    "language": "ka,ru"
+  }
+]
    • addedInput schema / properties / language
      Added value: +{
+  "description": "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\" for any requested language the entity has no label in.",
+  "type": "string"
+}
  3. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "id": "Q42"
+  },
+  {
+    "id": "Q1764"
+  }
+]
  4. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive. The description adds valuable context: it returns labels not codes, includes lastrevid and modified for state questions, and explains language fallback behavior. No contradictions with annotations.

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?

Front-loaded with the core distinction (human-readable labels), followed by usage guidance, an example, revision info, and language instructions. Every sentence adds value; the description is dense but efficiently organized without redundancy.

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?

Given the rich schema (100% coverage) and annotations covering safety, the description covers all necessary operational details: output format, revision fields, language handling, and how to obtain the Q-id. No critical information is missing for an agent to call it correctly.

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 the baseline is 3. The description reinforces that 'language' supports comma/pipe-joined lists and fallback, but the schema already contains this detail. The description does not introduce new parameter semantics beyond the schema, so a 3 is appropriate.

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+resource: returns structured facts about a Wikidata entity in human-readable form, explicitly distinguishing from get_entity by noting it resolves labels instead of raw codes. The example with Q42 clarifies the output shape. This is a clear, unambiguous purpose.

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 instructs to prefer this tool over get_entity for attribute/fact queries, names the alternative, and gives concrete query patterns (e.g., 'what is X's date of birth'). Also directs users to pass a Q-id from search_entities. This is precise routing guidance.

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

All Wikidata toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources