Skip to main content
Glama

Search Wikidata entities

search_wikidata
Read-only

Find Wikidata Q-ids for Swiss municipalities, cantons, mountains, lakes, companies and people by name. Filter to Swiss items by country or citizenship, then use the ID to fetch full entity data.

Instructions

Find Wikidata items (Q-ids) by name; the universal join key for Swiss municipalities, cantons, mountains, lakes, rivers, companies, people and institutions. Returns id, label, description and match. Set swiss_only=true to keep only items whose country (P17) or citizenship (P27) is Switzerland (Q39). Examples: 'Matterhorn', 'Lac Léman', 'Nestlé', 'ETH Zürich', 'Winterthur' (swiss_only=true). Follow up with get_wikidata_entity.

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": {
      "query": "<query>"
    },
    "name": "search_wikidata"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (1-50, default 10)
queryYesName or label to search, e.g. 'Matterhorn', 'Roche', 'Aare'
languageNoSearch/label language: de, fr, it, rm or en (default en)en
swiss_onlyNoRestrict to items with country or citizenship = Switzerland

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the readOnly/openWorld annotations, it discloses the return shape (id, label, description, match) and explains the exact semantics of swiss_only via P17/P27 against Q39, which is real behavioral detail. It still says nothing about ranking, fuzzy-match behavior, or what happens when nothing matches.

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 purpose and return fields, then filtering, then examples, then the follow-up call — a logical order that wastes little. The catalogue of entity types ('municipalities, cantons, mountains, lakes, rivers...') is slightly padded but does convey scope, and the whole thing remains a single tight block.

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 helpfully enumerates returned fields and explains the one non-obvious parameter, so an agent can call it and interpret results. Remaining gaps (result ordering, matching tolerance, behavior on zero hits) are minor for a simple read-only search.

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 coverage is already 100%, so the baseline is 3; the description adds genuine meaning by spelling out the P17/P27/Q39 filter logic behind swiss_only and by giving example values for query. limit and language semantics are left entirely to the schema.

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 ('Find Wikidata items (Q-ids) by name') and frames the result as the join key to other Swiss datasets. It also names the natural follow-up tool, get_wikidata_entity, so an agent can place it relative to siblings without opening schemas.

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

Usage Guidelines4/5

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

Gives concrete usage context: search by name for entities, set swiss_only to narrow to Switzerland-linked items, and chain into get_wikidata_entity. It supplies illustrative queries covering several entity types. It does not say when to prefer query_wikidata or a domain-specific search (e.g. search_companies) instead, so there is no explicit exclusion.

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