Skip to main content
Glama

Wikipathways

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

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

Adds many behavioral details beyond annotations: requires OAuth, returns subscription id, lists supported types with examples, describes delivery channels with constraints (SMS cap, webhook auto-disable). No contradictions with 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?

Well-structured and front-loaded with purpose; every sentence adds value. While lengthy, it's necessary detail for a complex tool with nested parameters.

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?

Fully complete description for a complex tool with 100% schema coverage. No output schema needed as return value is specified. Covers all required context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Adds significant meaning beyond the schema: explains each enumeration value with examples, provides detailed param format per type, and elaborates on delivery channel options and validations.

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?

Clearly states it creates a proactive monitoring subscription to a live-data event stream and returns the new subscription id. Differentiates from sibling tools like unsubscribe and 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 on account requirements (Pipeworx OAuth) and mentions alternative tools like recent_alerts for feed pull. However, no explicit when-to-use vs when-not instructions.

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

All Wikipathways 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

B3.3/5.0
Disambiguation1/5

The tool set is severely mismatched: only 3 of 34 tools (get_pathway, list_pathways, search_pathways) relate to WikiPathways while the rest form overlapping Pipeworx/Polymarket families (ask_pipeworx vs ask_pipeworx_beta vs ask_pipeworx_grounded; multiple polymarket_* tools) with unclear boundaries and overlapping purposes.

Naming Consistency2/5

Naming conventions are highly inconsistent: product-specific names (pipeworx_feedback, pipeworx_trending), generic memory verbs (remember, recall, forget), and mixed snake_case patterns with no unifying verb_noun structure. The names do not reflect the WikiPathways domain at all.

Tool Count1/5

34 tools is far too many for a WikiPathways server, which only needs a handful of pathway-related operations. Nearly all tools belong to unrelated domains (SEC, FDA, Polymarket, npm, etc.), making the set feel bloated and unfocused.

Completeness1/5

For the stated WikiPathways purpose, only get, list, and search are present—no create, update, or delete operations—leaving obvious lifecycle gaps. The extensive non-WikiPathways tools do not contribute to the server's apparent domain coverage and create dead ends for agents expecting pathway management.

Resources