Skip to main content
Glama

Wikidata entity details

get_wikidata_entity
Read-only

Fetch a Wikidata entity by Q-id to obtain de/fr/it/rm/en labels, descriptions, key statements with resolved values, Swiss identifiers, and Wikipedia links for verification and enrichment.

Instructions

Read one Wikidata item by Q-id: labels in de/fr/it/rm/en, description, the key statements with values resolved to labels (instance of, country, located in, coordinates, population, area, elevation, website, inception, headquarters, industry, …; up to max_properties), Swiss identifiers (BFS municipality code P771, HLS/DHS id P902, parliament id P1307), and de/fr/it/rm/en Wikipedia links. Examples: 'Q72' (Zürich), 'Q1374' (Matterhorn), 'Q11943' (ETH Zürich).

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>"
    },
    "name": "get_wikidata_entity"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesWikidata Q-id, e.g. 'Q72', or an entity URI
languageNoLanguage for resolved value labels (default en)en
max_propertiesNoMax properties to include (default 30)
max_values_per_propertyNoMax values per property (default 5)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only and open-world semantics, and the description adds real substance on top: value labels are resolved, statements are truncated by max_properties and max_values_per_property, and specific property codes (P771, P902, P1307) are called out. It does not say what happens for an unknown or non-existent Q-id, but the disclosure of resolution and truncation behavior is meaningful.

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?

The core action is front-loaded in the first clause, followed by a dense return-value inventory and short worked examples. The property enumeration is long but each item signals what data is available; the trailing ellipsis keeps it from becoming a complete catalogue. Slightly heavy but nothing is plainly wasted.

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

Completeness4/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 carries the return-value burden and does so well by listing the categories of content returned. Remaining gaps — error behavior for invalid ids, and whether requested properties absent from an item are omitted or null — are minor for a read tool whose safety profile is already declared.

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 every parameter is already documented, and the description largely restates that (Q-id input, language selection, the max_properties cap). It adds a little framing around what max_properties bounds, but no syntax or edge-case guidance beyond the schema. Baseline 3 is appropriate.

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 opens with a specific verb and resource — 'Read one Wikidata item by Q-id' — and enumerates the returned content (labels, description, resolved statements, Swiss identifiers, Wikipedia links). It is distinguishable from a search or SPARQL tool by its single-entity scope, though it never names its siblings 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?

Usage is only implied: an agent can infer this tool applies when it already holds a Q-id. There is no statement about when to use search_wikidata or query_wikidata instead, and no note on what to do if only a name is known. The examples clarify input format rather than tool selection.

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