Skip to main content
Glama

Rss2json

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).

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Added
  2. Removed
  3. Added

TDQS

A4.5/5.0
Behavior5/5

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

The description goes beyond the readOnlyHint annotation by disclosing critical behavioral details: snapshots are written on cache-miss (so gaps mean no scan), history is bounded by a 60-day TTL, decay is computed from daily closes of edge_pp_net (net of slippage), and expired opportunities reflect closed/resolved/arbed-away markets. These traits are not visible in annotations or schema, making the description highly transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Although long, the description is front-loaded with the core question, then efficiently structures args, response fields, and limitations. Every sentence contributes essential information: response formats (tracked, expired, snapshot_dates), interpretation guides (median lifespan as competition clock), and data caveats. No wasted words.

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?

With no output schema, the description fully specifies the return structure: tracked[], expired[], and snapshot_dates[], including each subfield's meaning. It also covers data provenance, limitations (TTL, daily closes), and edge cases (snapshot gaps). This makes the tool understandable and usable without additional documentation.

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?

The schema descriptions already fully cover both parameters (days and window) with defaults and constraints. The description adds minor context (e.g., 'snapshot family') but does not introduce meaning beyond what the schema provides. Since schema coverage is 100%, a baseline of 3 is appropriate.

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 tool's unique function: "Edge persistence and decay telemetry built from daily polymarket_edges snapshots." It answers a specific question ("how long has this edge existed and is it shrinking?") and distinguishes itself from sibling tools like polymarket_edges by focusing on historical trend and decay rather than current edges.

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 to use the tool: when you need to know if an edge is fresh or old and whether it is decaying. It implies the trade-off with fresh vs. stale edges but does not explicitly discuss alternatives or when-not-to-use. The context is clear enough to guide selection.

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

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

B3.3/5.0
Disambiguation2/5

Many tools serve overlapping purposes: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all query Pipeworx data in similar ways. Polymarket tools also heavily overlap. This leads to ambiguity for an agent trying to select the right tool.

Naming Consistency2/5

Tool names are inconsistent, mixing snake_case (ai_visibility_check), all lowercase (feed, forget), and underscore-separated verbs (ask_pipeworx_grounded, list_subscriptions). No consistent pattern is followed.

Tool Count2/5

With 32 tools, the server feels overloaded for its stated purpose of RSS-to-JSON conversion. Many tools are unrelated (e.g., prediction markets, entity profiles, memory) making the scope too broad for a focused server.

Completeness2/5

The tool set has notable gaps: only one RSS-related tool (feed), and missing basic operations like creating or updating entities. The heavy focus on Pipeworx and Polymarket leaves the core domain underserved.

Resources