Skip to main content
Glama

Funcheap

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.), description adds rich behavioral details: delivery channel behavior (feed always on, email/sms/webhook), phone verification, SMS cap, webhook auto-disable, and signing secret. No contradiction 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single paragraph with dense but organized information. Front-loaded with purpose and requirement. Could be more scannable with bullets or sections, but all content earns its place.

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 no output schema, description explains return value ('Returns the new subscription id'). Covers purpose, requirements, types, delivery options, and constraints. Missing error scenarios but sufficient for a subscription creation tool.

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 substantial meaning: type examples for each enum, detailed param structures for each subscription type, and explanation of delivery sub-properties (including webhook signing).

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.' Specific verb (create) and resource (subscription). Distinguishes from sibling tools like 'list_subscriptions' and 'unsubscribe'.

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 explicit requirement: 'Requires a Pipeworx OAuth account (anonymous + BYO cannot persist subscriptions).' Also lists supported types and delivery channels. Does not explicitly state when not to use, but context is clear.

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

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

A4.1/5.0
Disambiguation4/5

Most tools are distinct (event search, subscriptions, memory, Polymarket arbitrage, data lookups), but ai_visibility_check, scan_competitor_ai_presence, bet_research, polymarket_edges, and polymarket_arbitrage have overlapping purposes around competitive research and prediction-market edge-finding. The detailed descriptions disambiguate them, though an agent could confuse polymarket_edges with polymarket_arbitrage.

Naming Consistency4/5

Tool names are mostly descriptive and consistent: search_events, event, categories, tags are aligned; ask_pipeworx, compare_entities, entity_profile follow a similar pattern. However, polymarket_* tools have an odd mix of `polymarket_arbitrage`, `polymarket_fill_risk`, and `polymarket_edge_tracker`, and discover_tools/recent_alerts/recent_changes are consistent, mostly. Naming is quite consistent overall with minor deviations.

Tool Count3/5

At 35 tools, the count is heavier than typical MCP servers, but it reflects a broad service (Funcheap data + Pipeworx data platform + pred markets). Still, plenty of tools serve the same primary purpose (polymarket_, ask_pipeworx variants) so some pruning would improve the surface.

Completeness4/5

The surface appears complete for its domain: search/retrieve events, category/tag navigation, memory, subscriptions (create/list/cancel/pull), data lookups, entity resolution, comparisons, profiles, edge scanning, and feedback. Minor gaps include no direct 'update' on events (but events are static), and no pricing fetch tool separate from event text, though body text covers it.

Resources