Skip to main content
Glama

Feodotracker

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

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

Annotations already indicate readOnlyHint, openWorld, idempotent, and non-destructive. Description adds beyond: explains snapshot gaps, decay computation (from daily closes, not intraday), and TTL limits. 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?

Description is well-structured with purpose upfront, then response fields and limits. It could be slightly more concise, but every sentence provides necessary information with minimal fluff.

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 no output schema, description thoroughly explains return values: tracked[], expired[], snapshot_dates[] with details on content and computation. Covers limitations (60-day TTL, not intraday). Complete for the tool's complexity.

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 description coverage is 100%, but description adds defaults for 'days' (14, clamp 2-30) and 'window' (default '1wk'), and explains the meaning of 'window' as snapshot family. This adds 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, answering when an edge existed and if it is shrinking. It distinguishes from sibling polymarket_edges by focusing on time-series analysis.

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?

Description explains usage context: to differentiate between fresh and old edges. While it doesn't explicitly state when not to use, the purpose and response structure implicitly guide usage. Sibling tools are known, but no direct exclusion.

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

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

Multiple near-duplicate clusters exist: ask_pipeworx, ask_pipeworx_beta (explicitly identical to the stable router right now), and ask_pipeworx_grounded all route through the same 5,767-tool catalog, and six polymarket_* tools overlap heavily in surfacing bet/edge opportunities. The blocklist tools (list, recent, aggressive) are only weakly distinguished by time window and confidence, requiring careful reading to select correctly.

Naming Consistency2/5

Naming mixes several incompatible conventions: bare adjectives/nouns for blocklist tools (aggressive, list, recent), brand-prefixed compounds (polymarket_arbitrage, pipeworx_feedback), verb_noun pairs (check_ip, resolve_entity), and noun phrases (entity_profile, bet_research). The server name 'Feodotracker' appears nowhere in the tool names, and the blocklist cluster uses a completely different style from the data cluster.

Tool Count2/5

At 35 tools, the count exceeds the 25-tool threshold for 'too many', but the deeper issue is that roughly 31 tools serve a general data-lookup/prediction-market platform while only 4 serve the server's stated Feodotracker blocklist purpose. The count reflects two unrelated products merged into one MCP server rather than a well-scoped tool surface.

Completeness2/5

For the named Feodotracker domain, the surface is thin: list/check/recent cover basic blocklist access but miss historical lookups, per-entry threat intel, or export formats that a botnet tracker would need. For the data-lookup domain the 31-tool suite is impressively complete, but the two domains don't form a coherent whole—each leaves the other's lifecycle half-served.

Resources