Skip to main content
Glama

Gdacs

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

A3.8/5.0
Behavior1/5

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

The description claims to create a new subscription and returns a new subscription id, which directly contradicts the idempotentHint=true annotation. While it adds rich detail about auth, delivery, and limits, this fundamental contradiction makes it misleading about repeat-call behavior.

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-structured: purpose first, then supported types, delivery channels, and requirements. Every part earns its place, though a small amount of redundancy with the schema's parameter descriptions exists.

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 creation tool with no output schema, it covers return value, auth prerequisites, all subscription types with examples, delivery channels, rate limits, and failure behavior (webhook auto-disable). This is complete enough for an agent to select and invoke the tool correctly.

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?

With 100% schema coverage, the description still adds value by mapping concrete examples to specific types (e.g., sec_8k items:["5.02"] = officer change) and clarifying the meaning of delivery options beyond the schema's already-detailed descriptions.

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 specific verb-resource pair ('Create a proactive monitoring subscription to a live-data event stream') and clearly distinguishes the tool from its siblings (list_subscriptions, unsubscribe, recent_alerts) by focusing on the act of subscribing and returning a subscription id.

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?

It provides clear context for when to use the tool (setting up monitoring for specific event types) and how to configure it, but it never explicitly contrasts with alternatives like using 'events' or 'recent_alerts' for one-off checks, nor does it state when not to subscribe.

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

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

Most tools have clear, distinct purposes, but the three ask_pipeworx variants (especially ask_pipeworx_beta, identical to ask_pipeworx) and the six Polymarket tools overlap conceptually and could cause misselection. Detailed descriptions largely compensate, but the boundaries between some meta-tools (e.g., ask_pipeworx vs deep_research vs bet_research) require careful reading.

Naming Consistency3/5

All names are snake_case, but conventions are mixed: verb-first (ask_pipeworx, compare_entities, discover_tools), noun-first compounds (entity_profile, polymarket_arbitrage), and single-word nouns (event, events, rss). The pattern is predictable for common actions but inconsistent across the set, making it harder to guess names for related tasks.

Tool Count2/5

At 35 tools, the count is heavy and the server named 'Gdacs' includes many unrelated tools (Polymarket, npm scanning, AI visibility), indicating scope creep. Several tools could be consolidated (e.g., the ask_pipeworx family and multiple pattern-market scanners), and the breadth dilutes the disaster-alerting focus implied by the server name.

Completeness4/5

The surface covers core workflows: data querying (ask/research/validate), entity profiling, prediction-market analysis (arbitrage/edges/fill risk), and subscription management (create/list/cancel). Minor gaps exist, such as no direct fetch tool for a specific Pipeworx pack and limited GDACS event management (only read operations), but these are workable with the provided meta-tools.

Resources