Skip to main content
Glama

Ecos Kr

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

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

Beyond annotations (readOnlyHint=false, idempotentHint=true, destructiveHint=false), the description adds critical behavioral details: delivery channel caveats (phone verification, 10/day cap, webhook auto-disable), the always-on feed, and the one-time webhook 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?

The description is a single dense paragraph but front-loads the core purpose. It efficiently conveys all necessary information without fluff, though a more structured format (e.g., bullet points) could improve readability. Every sentence earns its place.

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 complexity (3 parameters, nested objects, no output schema), the description covers return value, prerequisites, type-specific parameters, and delivery details. It is mostly complete but could mention error handling or quota limits beyond the 10/day SMS cap.

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

Parameters4/5

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

The schema has 100% description coverage, so baseline is 3. The description adds significant value by providing concrete examples for each subscription type (e.g., 'sec_8k: {ticker:"AAPL", items?:["5.02","1.01"]}') and delivery nuances, enhancing understanding beyond the schema.

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 the action ('Create'), the resource ('proactive monitoring subscription'), and the return value ('Returns the new subscription id'). It distinguishes from sibling tools like 'unsubscribe' and 'list_subscriptions' by focusing on creation.

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 specifies the required OAuth account and limitations for anonymous/BYO users. It provides detailed context for when to use (e.g., for live-data event monitoring) but lacks explicit exclusions or comparisons to alternatives, though siblings are available.

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

All Ecos Kr 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
Disambiguation3/5

Several tool families overlap heavily: ask_pipeworx and ask_pipeworx_beta are functionally identical today, and the polymarket_edges/arbitrage/fill_risk/kalshi_spread family plus entity_profile/recent_changes/compare_entities cover adjacent jobs. The descriptions are detailed enough to separate them with careful reading, but an agent could easily select the wrong one without deep inspection.

Naming Consistency3/5

The set has recognizable prefixes like ecos_, ask_pipeworx, and polymarket_, but it also mixes verb_noun names (validate_claim, discover_tools), bare verbs (remember, forget, recall), reversed/gerund forms (bet_research, pipeworx_trending), and special tokens (generate_llms_txt). The naming is readable on a per-family basis but not predictable across the full surface.

Tool Count2/5

35 tools is above the comfortable range for a coherent tool set, and several entries are near-duplicates or wrappers: ask_pipeworx_beta is currently identical to ask_pipeworx, and scan_competitor_ai_presence wraps ai_visibility_check. The prediction-market and company-research families could be consolidated without losing capability.

Completeness4/5

For the server's broad scope, lifecycle coverage is strong: ECOS has search/items/get/indicators, subscriptions have create/list/read/cancel, memory has save/read/delete, and the data-research surface covers lookup, grounded verification, comparison, profiles, changes, and discovery. Minor gaps exist, such as no direct tool to fetch a pipeworx:// record by URI or execute a single catalog tool directly, but these are workable.

Resources