Skip to main content
Glama

Wikidata

by io.github.pipeworx-io

Wikidata Recent Changes

wikidata_recent_changes
Read-onlyIdempotent

Newest items created or edited on Wikidata right now, from the live MediaWiki recent-changes feed. Answers "which Wikidata item was created most recently", "what QIDs were created today", "what changed on Wikidata in the last hour", "recent edits to Wikidata items". Returns each change newest-first with its Q-id, revision id, previous revision id, UTC timestamp, editing user, edit comment and byte size, plus a cursor for paging further back.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoWhich changes to list: "new" for freshly created items (default), "edit" for edits to existing items, "all" for both.
userNoOnly changes made by this Wikidata username (e.g. "Dsp13").
limitNoMax changes to return (1-50, default 10).
sinceNoStop at this UTC timestamp, ISO 8601 (e.g. "2026-08-22T00:00:00Z"). Listing runs newest-first back to this point.
cursorNoContinue token from a previous call's "cursor" field, to page further back in time.
namespaceNoWikidata namespace: 0 = items/Q-ids (default), 120 = properties/P-ids, 146 = lexemes.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
hintNoHow to get a result when found is false
typeNoWhich changes were listed: new, edit or all
countNoNumber of changes returned
foundYesWhether any changes matched
cursorNoContinue token to page further back in time, or null at the end
reasonNoMachine-readable code when found is false (invalid_type, invalid_since, no_changes_in_window, or a Wikidata API error code)
sourceNoUpstream the rows came from
changesNoChanges newest-first
namespaceNoWikidata namespace listed (0 items, 120 properties, 146 lexemes)
most_recentNoQ-id of the most recent change, the first row
most_recent_timestampNoUTC timestamp of that most recent change

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already mark this read-only/idempotent/non-destructive, and the description adds live-feed recency, newest-first ordering, exact returned fields (Q-id, revision ids, timestamp, user, comment, byte size), and cursor-based paging. No annotation contradiction exists.

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?

Three sentences: what it returns, what questions it answers, and how results are shaped. Every sentence adds useful information and the key purpose is front-loaded.

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?

With rich annotations, a fully documented input schema, and an output schema, the description still adds ordering, live-feed behavior, and return-field details. Nothing needed to select or invoke the tool correctly is missing.

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 schema fully documents all six parameters. The description adds little parameter-level meaning beyond mentioning the cursor for paging, which the schema already covers.

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?

The description names a specific resource (Wikidata live MediaWiki recent-changes feed) and specific actions (newest items created or edited), and answers concrete example questions. The Wikidata qualifier separates it from the generic recent_changes sibling.

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?

The example questions provide clear context for when to use the tool, such as asking which QIDs were created today or what changed in the last hour. It does not explicitly state exclusions or name alternatives, so it stops short of a 5.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.5/5.0
Disambiguation2/5

The tool set is extremely heterogeneous and overlapping. Multiple tools serve nearly identical purposes (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, discover_tools, suggest_questions), and entity-related tools (get_entity, get_wikidata_facts, entity_profile, compare_entities, resolve_entity) have unclear boundaries. The server is named Wikidata but only 3 of 34 tools actually relate to Wikidata, causing confusion about which tool is appropriate.

Naming Consistency2/5

Tool names mix multiple conventions: verb_noun (get_entity, search_entities, list_subscriptions), noun phrases (polymarket_edges, entity_profile, pipeworx_feedback), and inconsistent suffixes (_beta, _grounded). The verbs used are vague and not part of a coherent pattern (get, search, ask, discover, resolve, scan, validate, generate, remember, recall). The naming is readable but lacks a predictable system.

Tool Count2/5

34 tools is high for a server with a focused name like Wikidata, and nearly all tools belong to unrelated domains (Pipeworx data routing, Polymarket betting, memory management, subscriptions, AI visibility). The count appears bloated and scattered rather than well-scoped; most tools could be split into separate servers.

Completeness2/5

For a Wikidata server, the coverage is minimal: only search, get by ID, and human-readable facts are present, with no SPARQL query support or property-level access. The majority of tools address Pipeworx's broad data catalog, leaving the advertised Wikidata purpose severely under-served. The surface is complete for a different domain but incomplete for the stated one.

Resources