Skip to main content
Glama

Wikidata Search Entities

wikidata_search_entities
Read-onlyIdempotent

Search Wikidata entities by label or alias (e.g., "Albert Einstein", "Python programming language", "Tokyo"). Returns entity IDs, labels, descriptions, and aliases. Useful for finding the Wikidata ID of any concept.

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": {
      "query": "Albert Einstein"
    },
    "name": "wikidata_search_entities"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results to return (1-50, default 10)
queryYesSearch query (e.g., "Marie Curie", "Bitcoin", "Great Wall of China")
languageNoLanguage code for labels (default "en"). E.g., "fr", "de", "ja"

Output Schema

NameRequiredDescriptionDefault
resultsYesArray of search results

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint and destructiveHint=false, so the safety profile carries no burden on the description. The description adds the shape of returned fields (IDs, labels, descriptions, aliases), which mildly helps, but says nothing about ordering, match quality, empty results, or rate limits that would go beyond structured data.

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?

Three short sentences with the operation front-loaded and examples immediately after, so an agent reads the essentials first. The final 'Useful for...' sentence is close to redundant with the first, costing it a point.

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?

For a three-parameter read-only search with full schema coverage, rich annotations and an output schema, the description covers purpose, inputs and return fields. Only marginal extras, such as result ordering or behavior on no matches, are absent and are not essential 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 description coverage is 100% with per-parameter descriptions for query, limit and language, so the schema fully documents the inputs. The description only adds illustrative query strings that mirror the schema examples, contributing little new semantics; baseline 3 applies.

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 states a specific verb and resource ('Search Wikidata entities by label or alias') and supplies three concrete example queries, so the operation is unambiguous. It stops short of naming or contrasting any sibling such as wikidata_get_entity or search_within, so differentiation relies on the reader's inference from names.

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 closing sentence 'Useful for finding the Wikidata ID of any concept' implies the use case, which is genuinely helpful context. However, there is no explicit when-not-to-use guidance and no pointer to an alternative for entity retrieval once an ID is known.

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.