Skip to main content
Glama

Paperswithcode

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

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

Annotations already indicate readOnly, openWorld, idempotent, and non-destructive. The description adds rich behavioral context: time-series details, first_seen, trend computation, decay rate, expired opportunities, lifecycle, and limitations (60-day TTL, daily close data). No contradictions.

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 well-structured with sections (LIMITS, RESPONSE). Every sentence provides useful information, though some details could be tightened. It earns its length given the tool's complexity.

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?

No output schema exists, but the description thoroughly explains return fields (tracked[], expired[], snapshot_dates[]) and their contents, plus behavioral constraints (e.g., TTL, data gaps). Complete for the tool's purpose.

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 baseline is 3. The description adds minor context (e.g., 'snapshot family') but largely mirrors schema defaults and constraints. No significant value 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 tool provides edge persistence and decay telemetry from daily snapshots, answering a specific question about edge duration and trend. It distinguishes itself from siblings like polymarket_edges by focusing on historical time-series rather than current snapshots.

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 implies usage context (e.g., differentiating between fresh and old edges) but lacks explicit when-to-use vs. alternatives or when-not-to-use guidance. It is clear enough for an agent to infer, but could contrast with polymarket_edges directly.

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

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

ask_pipeworx and ask_pipeworx_beta are currently identical in behavior, creating direct overlap. Additionally, the five query/research tools (ask_pipeworx, ask_pipeworx_grounded, deep_research, validate_claim, bet_research) and six Polymarket tools have heavily overlapping boundaries that require reading long descriptions to disambiguate.

Naming Consistency3/5

Names are uniformly snake_case and mostly readable, with consistent domain prefixes (polymarket_*, pipeworx_*) and a verb_noun majority (get_paper, search_papers, resolve_entity). However, bare-verb memory tools (remember, recall, forget) and adjective-noun names (recent_alerts, trending_papers, deep_research) break the dominant convention, making the set mixed though not chaotic.

Tool Count2/5

At 35 tools, this exceeds the 25+ threshold for 'too many,' and several are near-duplicates or overlapping query modes (ask_pipeworx vs ask_pipeworx_beta vs ask_pipeworx_grounded). The server bundles paper search, a universal data router, prediction-market analytics, memory, subscriptions, dependency scanning, and AI visibility into one surface, which feels over-scoped.

Completeness4/5

The surface is quite thorough for its broad domain: querying has grounded/deep/meta variants, companies have profile/compare/change/claim tools, prediction markets have research/edges/arbitrage/fill-risk/spread tracking, and subscriptions/memory have full lifecycles. Minor gaps exist (no full pack catalog listing, no direct fetch-by-URI tool, no paper leaderboards), but agents can work around them via discover_tools/ask_pipeworx.

Resources