Skip to main content
Glama

Codewars

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

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

The description goes well beyond the annotations. It details the mutation behavior (creating a subscription), the requirement for a specific account type, return value, delivery channels with constraints (phone verification, SMS cap, webhook auto-disable), and supported event types. This provides rich behavioral context.

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 well-structured with clear sections for type and delivery, and the first sentence effectively front-loads the purpose. While it is somewhat lengthy, every sentence contributes necessary information. Minor redundancy could be trimmed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (3 parameters, nested objects, no output schema), the description covers most aspects: account requirements, type-specific params, delivery options with constraints. However, it does not clarify idempotency behavior (though annotations indicate idempotentHint=true) or the exact structure of the returned subscription id. Still, it is quite thorough.

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?

Although the input schema already has 100% description coverage, the description adds significant value by providing concrete examples for each subscription type (e.g., 'sec_8k: items:["5.02"] = officer change') and detailed explanations of delivery options including webhook signature verification. This greatly enhances understanding beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool creates a proactive monitoring subscription and returns the subscription id. It specifies the resource (live-data event stream) and the verb (create). However, it does not explicitly differentiate from sibling tools like 'list_subscriptions' or 'unsubscribe', though the purpose is distinct enough.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description mentions the requirement for a Pipeworx OAuth account and notes that anonymous/BYO cannot persist subscriptions, implying appropriate use cases. However, it lacks explicit when-to-use vs. when-not-to-use guidance and does not mention alternatives among sibling tools.

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

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

The 4 Codewars tools (kata, user, user_authored, user_completed) are distinct, but the 31 Pipeworx tools create real overlap: ask_pipeworx, ask_pipeworx_beta (explicitly 'currently matches ask_pipeworx exactly'), and ask_pipeworx_grounded are near-twins of the same router, and the five polymarket_* tools (edges, arbitrage, edge_tracker, fill_risk, kalshi_spread) have heavily overlapping opportunity-discovery purposes. discover_tools and suggest_questions also both serve as 'what can I ask' entry points. Agents will misselect between the three ask_pipeworx variants and across the prediction-market suite.

Naming Consistency2/5

Naming conventions are mixed: bare nouns (kata, user), bare verbs (forget, remember, subscribe), adjective_noun (recent_alerts, recent_changes), verb_noun (validate_claim, bet_research), and noun_verb (user_authored, user_completed) all appear. Even within the small Codewars family the prefix style is inconsistent — kata and user are bare nouns while user_authored and user_completed expect a user_ prefix, and remember/recall/forget use a different verb style than the rest of the server.

Tool Count2/5

35 tools exceeds the 25+ 'too many' threshold for a coherent server. Worse, 31 of the 35 are Pipeworx meta-research tools unrelated to the server's namesake (Codewars), so the count is drastically inflated relative to its apparent purpose — the server presents a full finance/prediction-market/research gateway while contributing only 4 tools to its advertised domain.

Completeness2/5

The actual Codewars surface has significant gaps: kata, user, user_authored, and user_completed are purely read-only, with no solution submission, attempt/training history, leaderboard access, or kata search by difficulty/language. Meanwhile the Pipeworx side is over-complete for a server not named for it, leaving the server's stated identity under-covered with no way to perform any write operation on the Codewars platform.

Resources