Skip to main content
Glama

Complex Portal

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

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

Annotations are readOnlyHint=false, openWorldHint=true, idempotentHint=true, destructiveHint=false. Description adds significant context: requires OAuth, always-on feed, optional delivery channels with constraints (SMS cap, webhook HMAC signing, auto-disable after 10 failures). No contradictions.

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?

Description is somewhat long but well-structured with bullet points and examples. Front-loaded with core purpose. Could be slightly more concise, but every sentence is informative.

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?

No output schema provided, but description mentions return value ('new subscription id'). Covers all parameter types, delivery channels, constraints, and prerequisites. Sibling tools include unsubscribe and list_subscriptions, providing full lifecycle 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?

Schema coverage is 100%, but description adds invaluable type-specific parameter examples and constraints for each subscription type (e.g., sec_8k item codes, polymarket_edge topics, SMS format). This greatly aids the agent in constructing correct invocations.

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 clearly states 'Create a proactive monitoring subscription to a live-data event stream. Returns the new subscription id.' This is a specific verb and resource, and it effectively distinguishes 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?

Explicit requirement for Pipeworx OAuth account and that anonymous/BYO cannot persist. Explains supported types with examples. Does not explicitly contrast with alternatives like 'recent_alerts', but context is clear enough.

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

All Complex Portal 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.8/5.0
Disambiguation2/5

Multiple tools have overlapping boundaries: ask_pipeworx and ask_pipeworx_beta are explicitly identical, ask_pipeworx_grounded and deep_research heavily overlap with them, and entity_profile, compare_entities, recent_changes, and validate_claim all circle the same company-data space. The prediction-market cluster (polymarket_edges, polymarket_edge_tracker, polymarket_arbitrage, polymarket_fill_risk, polymarket_kalshi_spread) also requires careful reading to distinguish. The descriptions help, but the set relies on them to disambiguate near-duplicates.

Naming Consistency4/5

Nearly all tools follow a consistent lowercase snake_case style, whether verb_noun (search_complexes, validate_claim, unsubscribe), noun_verb (entity_profile, recent_changes), or brand-like (ask_pipeworx, polymarket_edges). There is no camelCase mixing or chaotic verb style. Minor inconsistency exists between imperative verbs (remember, forget, subscribe) and noun-style names, but the overall pattern is readable and predictable.

Tool Count2/5

33 tools is well above the 25-tool 'heavy' threshold, and many are meta-tools (discover_tools, suggest_questions, pipeworx_feedback, pipeworx_trending, remember/recall/forget) that pad the surface. The server is named 'Complex Portal', yet only two tools serve that purpose—the rest belong to a broad data platform. The count feels inflated and misaligned with the server's stated identity.

Completeness3/5

For the broad Pipeworx data platform the surface is fairly complete: universal querying, grounded answers, deep research, entity profiles, comparisons, claim validation, subscriptions, memory, and feedback. For the Complex Portal domain named by the server, coverage is thin—just search and fetch-by-accession, with no browsing, species filtering, or cross-reference tools. The core workflow works, but the namesake domain is under-served relative to the rest of the set.

Resources