Skip to main content
Glama

Watchmode

by io.github.pipeworx-io

Polymarket Edge Tracker

polymarket_edge_tracker
Read-onlyIdempotent

Edge persistence and decay telemetry built from daily polymarket_edges snapshots. Answers "how long has this edge existed and is it shrinking?" — a fresh wide edge and a 3-week-old wide edge are different trades (the latter is wide for a reason nobody is willing to take). Args: days (lookback, default 14, max 30), window (snapshot family, default "1wk"). RESPONSE: tracked[] = every opportunity in the LATEST snapshot with its full edge_pp_net time-series across prior snapshots, first_seen, trend (new | widening | stable | decaying) and decay_pp_per_day (both computed on |edge_pp_net| — the value itself is signed by trade direction, negative = SELL YES); expired[] = opportunities that appeared in earlier snapshots but are GONE from the latest (closed, resolved, or arbed away) with their lifespan_days — the median lifespan is your competition clock; snapshot_dates[] = which days actually have data (snapshots are written when polymarket_edges runs on a cache-miss, so gaps mean nobody scanned that day). LIMITS: history depth is bounded by the 60-day snapshot TTL and starts from when snapshotting was enabled; decay numbers come from daily closes of edge_pp_net (net of default slippage), not intraday.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoLookback in days (default 14, clamp 2-30).
windowNoWhich polymarket_edges window family to read snapshots for: 24hr | 1wk | 1mo (default 1wk).

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already indicate the tool is read-only, idempotent, and non-destructive. The description adds significant detail: it explains data freshness (daily closes, not intraday), TTL bounds (60-day snapshot TTL), and the meaning of expired opportunities (gone from latest snapshot). No contradictions 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 fairly long but information-dense. Every sentence serves a purpose, and the structure is clear: purpose, arguments, response fields, limitations. It could be slightly more concise, but the level of detail is justified.

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?

Despite lacking an output schema, the description thoroughly explains the return structure: tracked[] (with fields like first_seen, trend, decay_pp_per_day), expired[] (with lifespan_days), and snapshot_dates[]. It also covers data limits and snapshot availability, leaving no gaps in understanding.

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

Parameters3/5

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

Schema coverage is 100%, so the baseline is 3. The description restates the default and clamping for 'days' and the default and options for 'window', but does not add new information beyond what the schema already provides.

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 explicitly states that the tool provides edge persistence and decay telemetry, answering 'how long has this edge existed and is it shrinking?' It distinguishes itself from sibling 'polymarket_edges' by building on top of its snapshots to track historical behavior.

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 clear context for when this tool is useful (e.g., comparing fresh vs. old edges) but does not explicitly mention alternatives or when not to use it. The guidance is implied through the example, but lacks explicit exclusions.

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

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

The server packs in three near-identical question-answering entry points (ask_pipeworx, ask_pipeworx_beta which explicitly states it 'currently matches ask_pipeworx exactly', and ask_pipeworx_grounded), plus overlapping research tools like deep_research and validate_claim — an agent can easily misroute. The Watchmode cluster also blurs title_search vs list_titles and list_titles vs releases. The very detailed descriptions save it from a 1, but the ask_pipeworx_beta duplicate is a genuine selection hazard.

Naming Consistency4/5

Everything is snake_case and the clusters follow good prefixes — title_detail/title_search/title_seasons/title_sources, polymarket_edges/polymarket_arbitrage/polymarket_fill_risk, ask_pipeworx/ask_pipeworx_beta/ask_pipeworx_grounded. Minor inconsistency: scan_competitor_ai_presence and ai_visibility_check are sibling tools but don't share a naming pattern, and the pipeworx_*/ask_pipeworx*/plain-noun (genres, sources, regions) mix is slightly uneven. Still readable and mostly predictable.

Tool Count2/5

41 tools is heavy, but the real problem is scope: only ~10 of them are Watchmode streaming tools, while the rest are a Pipeworx data-router suite, a Polymarket/Kalshi prediction-market suite, memory, subscriptions, npm scanning, and llms.txt generation. This isn't a focused Watchmode server — it's three or four unrelated product surfaces bolted together under one name. Any single coherent feature area would justify closer to 10-15 tools.

Completeness3/5

The Watchmode core is actually well covered for a read-only catalog: search, detail, seasons/episodes, source availability, releases, and directory tools (genres/regions/networks/sources) make a complete browse-to-detail flow. But the overall surface is unfocused — AI visibility, npm deps, and llms.txt have nothing to do with the apparent purpose — and several tools are gated (deep_research needs an account, ask_pipeworx_grounded costs extra, ai_visibility_check needs a BYO key), leaving dead ends for anonymous agents.

Resources