Skip to main content
Glama

Openligadb

by io.github.pipeworx-io

Subscribe to Alerts

subscribe
Idempotent

Create a proactive monitoring subscription to a live-data event stream. Returns the new subscription id. Requires a Pipeworx OAuth account (anonymous + BYO cannot persist subscriptions). Supported types: "sec_8k" (8-K filings matching ticker + item codes — e.g. items:["5.02"] = officer change), "polymarket_edge" (Polymarket↔Kalshi cross-venue mispricings — params:{topic:"fed"}), "fred_series" (new FRED observations — params:{series_id:"UNRATE"}). Delivery channels: feed (always on — pull via recent_alerts or GET registry.pipeworx.io/alerts.json), and optionally email (set delivery:{email:"you@x.com"}) or sms (delivery:{sms:"+15551234567"} — phone must be verified at /account first; 10/day cap).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesSubscription type.
paramsYesType-specific filter. sec_8k: {ticker:"AAPL", items?:["5.02","1.01"]}. polymarket_edge: {topic:"fed", min_spread_bps?:500}. fred_series: {series_id:"UNRATE"}. patent_grant: {applicant:"Apple Inc."}. clinical_trial: {sponsor?:"Pfizer", condition?:"lung cancer", phase?:"PHASE3"} (sponsor or condition required).
deliveryNoOptional delivery channels in addition to the always-on persistent feed. {email:"you@x.com"} sends a templated alert per fired event. {sms:"+15551234567"} sends an SMS per event — must match the verified phone on the caller's account (verify at https://pipeworx.io/account first; 10/day cap). {webhook:"https://..."} POSTs each event JSON to your endpoint, HMAC-signed — the response includes delivery.webhook_secret (whsec_…) ONCE; verify X-Pipeworx-Signature = sha256 HMAC of "<X-Pipeworx-Timestamp>.<raw body>". Auto-disabled after 10 consecutive failing runs.

TDQS

A4.4/5.0
Behavior4/5

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

The description discloses key behaviors: the subscription is created (non-read-only), requires authentication, supports specific types with example parameters, and delivery channels (feed always on, optional email/SMS with limits, webhook with HMAC signing). It adds value beyond annotations, which only hint at idempotency and open-world.

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?

The description is thorough but not overly verbose. It front-loads the primary purpose and returns type, then details types and delivery. Every sentence adds value, though some repetition with schema descriptions could be trimmed. Still, it is efficiently structured.

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?

Given the tool's complexity (nested objects, three parameters, no output schema), the description compensates fully. It covers all subscription types, parameter constraints, delivery channels with limits and prerequisites, and even mentions a signing secret. No significant gaps remain.

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?

Although the input schema provides 100% coverage with property descriptions, the tool description adds significant context: it provides concrete examples for each subscription type (e.g., sec_8k with items:['5.02']) and elaborates on delivery channel semantics (SMS cap, webhook signing process, phone verification requirement).

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 clearly states the tool's purpose: 'Create a proactive monitoring subscription to a live-data event stream. Returns the new subscription id.' It uses a specific verb ('create'), identifies the resource ('subscription'), and distinguishes from sibling tools like 'list_subscriptions' and 'unsubscribe'.

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 description provides explicit context for when to use this tool (proactive monitoring of live events) and outlines requirements (Pipeworx OAuth account). It does not directly specify when not to use it or list alternatives, but the detail on supported types and delivery channels helps the agent decide.

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