Skip to main content
Glama

Openligadb

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.5/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds that mark_read affects subsequent calls by tracking reads, which provides useful behavioral context beyond annotations.

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?

Every sentence is valuable and efficiently communicates purpose, filters, behavior, and alternative access. No fluff, well 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?

Despite no output schema, the description lists returned fields (source, citation_uri, raw payload) and mentions polling suitability and an HTTP alternative. Complete for a read-only filter tool.

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 100%, so baseline is 3. The description adds examples (e.g., 'sec_8k') and clarifies the effect of mark_read, enriching the meaning beyond 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?

Description opens with a specific verb+resource: 'Pull fired events from your subscription feed.' It clearly states the tool retrieves recent alerts with specific fields and filtering options, distinguishing it from siblings like list_subscriptions.

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?

Provides context for polling and points to an alternative via HTTP API for scripts/dashboards. However, it does not explicitly state when not to use this tool versus other sibling tools, lacking exclusion guidance.

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

All Openligadb 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
Disambiguation4/5

Most tools have clearly distinct purposes, with detailed descriptions differentiating similar tools like ask_pipeworx, ask_pipeworx_grounded, and deep_research. However, some overlap exists between ask_pipeworx and ask_pipeworx_beta, as both serve as universal routers with only minor routing improvements.

Naming Consistency2/5

Tool names follow inconsistent patterns: some use snake_case (ask_pipeworx, entity_profile), others use lowercase single words (forget, recall), and some use camelCase (bet_research, deep_research). This mix of conventions makes the naming scheme unpredictable.

Tool Count3/5

With 35 tools, the server covers a wide range of data sources, but the count feels slightly heavy for the apparent scope. Several tools serve meta-purposes (discover_tools, suggest_questions) or specialized functions (polymarket_arbitrage), adding to the complexity.

Completeness4/5

The tool set offers comprehensive coverage for financial, economic, drug, and news data, including comparison and grounding capabilities. However, the football-related tools are limited to German leagues, leaving a minor gap for other sports or regions.

Resources