Skip to main content
Glama

Stat Lv

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. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare read-only/non-destructive, so description adds substantial behavioral detail: snapshot generation on cache-miss implies gaps, 60-day TTL bound, daily-close basis of decay, and expired opportunity semantics. This exceeds annotation value and informs interpretation.

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?

Well-structured with labeled Args/Response/Limits sections, front-loading the core question. Although it is lengthy, every section adds necessary interpretive information and the density 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?

No output schema exists, but the description fully specifies response fields (tracked, expired, snapshot_dates), their subfields, and interpretation caveats. It also covers data availability limitations, making it sufficiently complete for a read-only telemetry tool.

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 covers both parameters with defaults, clamp ranges, and enum values, so baseline is 3. Description adds the notion of lookback history and snapshot family context, but mostly restates schema details.

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?

Clearly defines tool as edge persistence/decay telemetry from daily polymarket_edges snapshots, distinguishing it from sibling polymarket_edges by focusing on time-series, first_seen, trend, and decay. The specific question it answers makes its scope unmistakable.

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?

States the exact analytical question and contextualizes why old wide edges matter differently, giving implicit guidance on when to use. However, it does not explicitly name sibling alternatives or state when not to use, so it stops short of full exclusion guidance.

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

All Stat Lv 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
Disambiguation3/5

Several tools form overlapping families (ask_pipeworx/ask_pipeworx_beta/ask_pipeworx_grounded/deep_research, plus the six polymarket_* tools), and ask_pipeworx_beta is currently an exact behavioral duplicate. The long descriptions usually disambiguate them, but an agent could still struggle to quickly choose between similar research and edge-detection tools.

Naming Consistency3/5

Names are uniformly snake_case and prefix families like pipeworx_* and polymarket_* help, but there is no consistent verb_noun pattern: subjects, table_meta, recent_alerts, and entity_profile are noun phrases while remember, generate_llms_txt, and compare_entities are action-first. The mixed conventions are readable but less predictable than a uniform pattern.

Tool Count2/5

34 tools is well into the 'too many' range for a single tool set, even if each is individually documented. Several could plausibly be consolidated, such as ask_pipeworx_beta, the polymarket edge tools, and the AI-visibility pair.

Completeness4/5

For its broad stated purpose, the set covers the full lifecycle: lookup/research, entity profiles, comparisons, claim validation, prediction-market edge analysis, memory, subscriptions, and discovery. Minor gaps exist, such as no direct fetch-by-URI tool or subscription update path, but most workflows have a clear route.

Resources