Skip to main content
Glama

Wayback

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

TDQS

A4.7/5.0
Behavior5/5

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

Discloses beyond annotations: response structure (tracked, expired, snapshot_dates), fields (edge_pp_net time-series, first_seen, trend, decay_pp_per_day, lifespan_days), and limitations (60-day snapshot TTL, decay computed from daily closes not intraday). Annotations already indicate read-only, open-world, idempotent, non-destructive; description adds detailed 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.

Conciseness5/5

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

Description is concise yet comprehensive: two sentences on purpose, then a structured breakdown of the response, followed by limitations. Every sentence adds essential information without redundancy.

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, the description fully explains the response structure: tracked[] with time-series and computed fields, expired[] with lifespan_days, and snapshot_dates[]. It also explains limits like TTL and computation basis, making the tool's behavior fully understandable.

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?

Schema covers all parameters with descriptions including defaults and clamp. Description adds 'lookback default 14, max 30' for days and 'default 1wk' for window, providing a bit more usage context. Schema already has these details, so description adds minor value beyond 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?

Description clearly states the tool provides edge persistence and decay telemetry from daily snapshots, answering how long an edge has existed and whether it is shrinking. It contrasts with a fresh wide edge vs. a 3-week-old one, distinguishing it from sibling tools like polymarket_edges which likely provide current edge data.

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?

Implicitly guides usage by explaining the significance of edge age: 'a fresh wide edge and a 3-week-old wide edge are different trades' and that the latter is wide for a reason. It does not explicitly state when not to use it, but the context is clear enough for an AI agent to decide.

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

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

Several tool clusters overlap heavily: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are near-identical in purpose, and the five polymarket_* tools all target prediction-market analysis. The presence of a broad Pipeworx data layer alongside Wayback-specific tools under one server name further blurs boundaries.

Naming Consistency3/5

Most tools use snake_case, but the pattern varies: many follow verb_noun (get_snapshot, list_snapshots, resolve_entity, validate_claim), while others are noun_noun (entity_profile, polymarket_edges, pipeworx_feedback, bet_research). Suffixes like _beta and _grounded are used inconsistently, and some names are long and descriptive while others are terse.

Tool Count2/5

34 tools is far more than what a Wayback Machine server should need, and most tools (Pipeworx data queries, prediction-market analysis, memory, subscriptions) have nothing to do with the Wayback Machine. The server's stated purpose appears narrow, but the tool set is bloated with unrelated functionality.

Completeness2/5

For the Wayback Machine domain, only three tools are relevant (get_capture_count, get_snapshot, list_snapshots), and obvious operations like saving/archiving a URL, comparing snapshots, or handling deleted captures are missing. The Pipeworx-related tools are broad but not clearly aligned with the Wayback theme, so the core purpose is under-served.

Resources