Skip to main content
Glama

Dockerhub

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

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

Discloses that a new subscription id is returned, details supported types with examples, and explains delivery channels with constraints (email validation, SMS verification, 10/day cap, webhook signature). No mention of idempotency, though annotations indicate idempotentHint=true; no contradiction.

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 dense but well-organized: purpose first, then auth requirement, then supported types with examples, then delivery channels. Every sentence adds value; could be more bulleted but is efficient.

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?

Covers auth, types, params, delivery options, and constraints. No output schema exists, so return value is described. Missing potential error conditions or rate limits beyond SMS, but for a complex tool it is thorough.

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% with descriptions for each parameter. The description adds concrete examples for each type's params and elaborates on delivery channels (e.g., webhook signing, SMS cap). This exceeds baseline 3 for high coverage.

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 begins with 'Create a proactive monitoring subscription to a live-data event stream,' which clearly indicates the tool's action (create) and resource (subscription). It distinguishes from sibling tools like 'list_subscriptions' and 'unsubscribe' by specifying creation.

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 states the requirement for a Pipeworx OAuth account and that anonymous/BYO cannot persist subscriptions, providing a clear prerequisite. It does not explicitly mention alternatives or when not to use, but sibling names give context.

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

All Dockerhub 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.6/5.0
Disambiguation2/5

Many tools overlap in purpose, e.g., ask_pipeworx, ask_pipeworx_grounded, deep_research, entity_profile, and validate_claim all perform data lookups with subtle differences. Polymarket tools also have overlapping scopes. The large number of tools with similar functions creates confusion.

Naming Consistency3/5

Names are inconsistent: some use verb_noun (get_image, list_subscriptions), others are descriptive phrases (ai_visibility_check, bet_research), and some are single words (forget, recall). No clear pattern.

Tool Count2/5

33 tools is high, and many are unrelated to Dockerhub. The server name suggests a focused Docker toolset, but the bulk of tools are for Pipeworx/Polymarket/data lookups, making the count excessive for the advertised domain.

Completeness2/5

As a Dockerhub server, it lacks basic Docker operations like push, delete, or manage repositories. As a general data toolset, it covers many domains but still misses some core operations (e.g., no tool for searching inside images).

Resources