Skip to main content
Glama

wikidata_entity

Look up Wikidata entities by Q-id or search text to retrieve labels, descriptions, aliases, key claims, and Wikipedia links in a chosen language.

Instructions

Wikidata entity lookup by Q-id or search text: label, description, aliases in a chosen language, key claims (instance of, country, coordinates, inception, website, population, HQ, founders, industry, identifiers such as LEI/ticker/ISNI…) with resolved labels, Wikipedia link. Costs 0.002 USDC on Base per successful call (x402). Without a payment key this tool returns the 402 challenge.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
qNoSearch text (alternative)
idNoQ-id
langNoLanguage code, default en

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the key behavioral facts: a 0.002 USDC cost on Base per successful call via x402 and a 402 challenge when no payment key is present. It omits what happens on failed lookups, whether pricing applies to errors, and precedence when both id and q are supplied.

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?

Purpose and access modes are front-loaded in a single dense sentence, with the cost/payment caveat immediately after. The long enumeration of claim types is justified as return-value documentation given there is no output schema, though the trailing ellipsis list is somewhat sprawling.

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 and no annotations, the description does the necessary work: it names the returned fields, states the language behavior, and discloses the payment model. The remaining gaps (error behavior, id/q precedence) are minor for a three-optional-parameter lookup tool.

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 the baseline is 3; the schema already labels q as search text, id as Q-id, and lang as a language code defaulting to en. The description adds only mild value by noting that labels, descriptions and aliases are returned in a chosen language, but it does not clarify the id-vs-q conflict case.

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 ('Wikidata entity lookup by Q-id or search text') and enumerates the returned content (label, description, aliases, claims, Wikipedia link), so an agent knows exactly what it gets. It does not explicitly differentiate itself from siblings such as lei_lookup, though no sibling appears to overlap with generic Wikidata entity retrieval.

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?

It implies the two access modes (Q-id lookup or free-text search) and notes the payment prerequisite, which is real usage context. However, it gives no explicit when-to-use/when-not guidance, no guidance on choosing between the id and q parameters, and no routing toward any alternative tool.

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