Skip to main content
Glama

Data Seattle

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

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

Annotations already indicate readOnly, openWorld, idempotent, not destructive. Description adds extensive behavioral detail: response structure (tracked, expired, snapshot_dates), decay computation on absolute value, signed interpretation, daily closes not intraday, 60-day TTL, snapshot start condition. Goes well beyond 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 dense and informative, but somewhat long. Every sentence adds value. Minor inefficiency: parenthetical about negative sign could be in parameter description. Overall well-structured and front-loaded with purpose.

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, so description fully explains return values: tracked array with time-series, first_seen, trend, decay; expired array with lifespan; snapshot_dates. Covers caveats (TTL, daily nature, snapshot gaps). Complete for a complex 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 coverage is 100% with detailed descriptions including defaults and ranges. Description restates defaults ('days default 14, max 30'; 'window default 1wk') but adds no new semantics beyond schema. Baseline 3 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?

Describes specific verb+resource: 'Edge persistence and decay telemetry built from daily polymarket_edges snapshots.' Clearly answers 'how long has this edge existed and is it shrinking?' Distinguishes from sibling 'polymarket_edges' by focusing on persistence and decay rather than raw 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?

Explains when to use: to differentiate between fresh and old edges. Provides concrete example (fresh vs 3-week-old edge). Lists limits (60-day TTL, snapshot gaps). Does not explicitly state when not to use or compare directly to all siblings, but context is clear.

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

All Data Seattle 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

A4.1/5.0
Disambiguation3/5

Many tools have distinct purposes, but the ask_pipeworx variants (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded) and the prediction market tools (bet_research, polymarket_edges, polymarket_arbitrage) can cause confusion due to overlapping functionality. Some tools like 'seattle_recent' are vague.

Naming Consistency4/5

Most tools follow a consistent verb_noun or noun_verb pattern (e.g., validate_claim, resolve_entity). However, a few like 'seattle_recent' and 'pipeworx_trending' deviate slightly, and 'recent_alerts' mixes noun_verb.

Tool Count2/5

34 tools is excessive for a single server, covering data retrieval, prediction markets, Seattle data, memory, subscriptions, and utility. The broad scope feels bloated and overwhelming, making it hard for agents to find the right tool.

Completeness4/5

The server covers a wide array of domains with good depth in data retrieval and prediction markets. Minor gaps exist (e.g., Seattle tools limited to four datasets, no other city data), but overall it addresses most use cases its tools suggest.

Resources