Skip to main content
Glama

Remoteok

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?

Beyond annotations (readOnlyHint=false, idempotentHint=true, etc.), the description adds critical behavioral details: OAuth requirement, always-on feed, optional delivery channels with verification and rate limits, webhook signing secret one-time return, and auto-disable after failures. This fully informs the agent about side effects and constraints.

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 comprehensive but slightly lengthy. It uses well-structured bullet points for types and delivery channels, front-loading the core action. A bit more conciseness could be achieved, but it remains efficient.

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 complexity (3 params, nested objects, no output schema), the description covers all essential aspects: authentication, type-specific filters, delivery options with limitations, and behavioral traits like one-time webhook secret. It leaves no critical gaps for an AI agent.

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 the description adds extensive value: detailed examples for each type in params, constraints for delivery fields (e.g., E.164 phone, webhook HTTPS only), and clarification of required fields (sponsor or condition for clinical_trial). This far exceeds baseline.

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 'Create a proactive monitoring subscription to a live-data event stream' with a specific verb and resource. It distinguishes from sibling tools like 'unsubscribe' and 'list_subscriptions' by detailing the creation aspect and return of 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?

The description provides explicit context: requires Pipeworx OAuth account, lists supported types and delivery channels, and mentions constraints (e.g., 10/day SMS cap, webhook auto-disable). It does not explicitly exclude use cases but offers enough guidance for correct invocation.

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

All Remoteok 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
Disambiguation2/5

Several tool clusters have fuzzy boundaries: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all answer questions through the same routing layer, while polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker, polymarket_fill_risk, and bet_research all address prediction-market edges. Even with detailed descriptions, an agent can easily select the wrong variant.

Naming Consistency3/5

Names are uniformly lowercase snake_case and many follow a verb_noun pattern (list_jobs, search_jobs, resolve_entity, validate_claim), but there are numerous noun-first and adjective-first exceptions (entity_profile, recent_alerts, pipeworx_trending, polymarket_arbitrage) plus bare verbs (remember, forget, recall, subscribe). The pattern is readable but not consistently applied.

Tool Count2/5

34 tools is well above the well-scoped range, and the vast majority are not about the server's RemoteOK namesake. The set appears to merge several distinct domains (Pipeworx data research, Polymarket betting, RemoteOK jobs, memory utilities) into one oversized surface, making it feel more like a bundled platform than a focused server.

Completeness4/5

For the dominant Pipeworx/data-research theme, coverage is strong: question answering, grounded verification, entity profiles, comparisons, change feeds, discovery, memory, subscriptions, and citation-based research are all present. The RemoteOK job subset covers list/search/get without obvious dead ends. Minor gaps exist (no direct citation-URI fetcher, no job alert subscriptions), but agents can work around them.

Resources