Skip to main content
Glama

wikipedia

by io.github.pipeworx-io

Recent Alerts

recent_alerts
Read-onlyIdempotent

Pull fired events from your subscription feed. Returns the most recent alerts the evaluator has written to your persisted feed — each carries source, citation_uri (pipeworx:// when available), and the raw event payload. Filter by type (e.g. "sec_8k") and/or since (ISO timestamp). Set mark_read:true to flag returned events read so the next call only shows newer ones. Polls work fine; the same feed is also at GET registry.pipeworx.io/alerts.json for scripts and dashboards.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoOptional — filter to one subscription type.
limitNoMax events to return (1-200, default 50).
sinceNoOptional ISO timestamp — return events fired_at >= this time.
mark_readNoFlag the returned events read in the same call (default false).
unread_onlyNoReturn only events where read_at is null (default false).

TDQS

A4.7/5.0
Behavior5/5

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

Despite the readOnlyHint annotation, the description transparently discloses that mark_read:true causes a side effect (flags events read, affecting subsequent calls). It also explains the persisted feed and polling behavior, adding material context beyond the annotations. This is not a contradiction because the primary operation is read-only and the side effect is clearly flagged as optional.

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?

Four concise sentences, each earning its place: purpose, return format, filtering flags, and polling/alternate access. Front-loaded and free of fluff.

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?

For a read-oriented tool with five optional parameters and no output schema, the description covers return fields, filtering, read-state management, polling suitability, and an alternative access method. It provides sufficient context to invoke correctly without missing critical details.

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?

The schema covers all parameters with descriptions (100% coverage), so the baseline is 3. The description adds value by giving a concrete example for type ('sec_8k'), clarifying the consequence of mark_read ('so the next call only shows newer ones'), and reinforcing that since accepts ISO timestamps. This extra semantic layer justifies a 4.

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 opens with a clear verb and resource: 'Pull fired events from your subscription feed.' It distinguishes itself from sibling tools by focusing on subscription alerts, the persisted feed, and its own retrieval semantics. The return fields (source, citation_uri, raw payload) further solidify the purpose.

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?

Context is clear: the tool is for retrieving recent alerts and supports polling ('Polls work fine'). It mentions an alternative HTTP endpoint for scripts/dashboards, but does not explicitly contrast with sibling tools. The absence of exclusions or a direct 'when-not-to-use' keeps it from a 5.

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

All wikipedia 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.9/5.0
Disambiguation2/5

Several tool families have ambiguous boundaries: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are three variants of the same router (with beta currently identical), and the six polymarket tools plus bet_research heavily overlap in scanning and pricing edges. discover_tools, suggest_questions, and deep_research also all function as 'what should I query' entry points. Agents will struggle to select the right tool without carefully reading long descriptions.

Naming Consistency3/5

Many tools follow a clear verb-first snake_case pattern (get_article_extract, resolve_entity, subscribe, validate_claim), and families like ask_pipeworx_* and polymarket_* are internally consistent. However, notable noun-phrase outliers such as entity_profile, deep_research, bet_research, recent_changes, pipeworx_feedback, and polymarket_edge_tracker break the convention. The naming is readable but not predictable across the full set.

Tool Count2/5

36 tools is well over the 25+ threshold for a typical MCP server, and for a server named 'wikipedia' it is especially disproportionate: only 5 tools actually deal with Wikipedia while 31 are Pipeworx data, prediction-market, memory, subscription, and feedback utilities. The count reflects a broad all-in-one platform crammed into a Wikipedia-labeled surface rather than a well-scoped server. This is a significant scope mismatch.

Completeness4/5

The Wikipedia portion is reasonably complete for read-only lookup: search, summary, sections, full extract, and random discovery cover common encyclopedic questions without dead ends. The broader Pipeworx surface is also extensive, with query, grounded verification, deep research, entity resolution/profile/comparison, claim validation, memory, and subscription lifecycle tools. Minor gaps remain (no article categories/history, no update for subscriptions, no direct fetch of a citation URI), but they are workable.

Resources