Skip to main content
Glama

Mime

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

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

Annotations already declare safe read-only behavior, and description adds substantial behavioral details: time-series, trend classification, decay computation, snapshot gaps, and limits (60-day TTL, daily closes). 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.

Conciseness5/5

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

Description is compact but information-dense. Front-loads the core purpose, then systematically covers arguments, response fields, and limits. Every sentence adds value.

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 defines the response structure (tracked, expired, snapshot_dates) with field explanations and limits. Complete for a tool of this complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema coverage, baseline is 3. The description adds significant meaning: explains days clamping (2-30), window family options, and the full response structure (tracked/expired/snapshot_dates) with field semantics, far exceeding the schema's minimal descriptions.

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 explicitly states the tool answers 'how long has this edge existed and is it shrinking?' with a specific verb-resource combination (edge persistence telemetry). It clearly distinguishes from sibling polymarket_edges, which likely returns current edges without historical context.

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?

Provides context on when to use: to differentiate between fresh and old edges. Implies usage for assessing edge persistence but does not explicitly state when not to use or list alternative tools.

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

All Mime 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/5.0
Disambiguation3/5

Several tools have overlapping purposes, such as the ask_pipeworx family (standard, beta, grounded) and the multiple Polymarket analysis tools (edges, arbitrage, fill_risk, edge_tracker, kalshi_spread, bet_research). The detailed descriptions help differentiate them, but an agent could still misselect between deep_research vs ask_pipeworx or polymarket_edges vs polymarket_arbitrage.

Naming Consistency3/5

Naming patterns are mixed: many tools use verb_noun (discover_tools, validate_claim, compare_entities), but others are noun_noun (entity_profile, polymarket_edges), single verbs (remember, recall, forget), or unusual forms (extension_for, search_within, ask_pipeworx). The polymarket_ prefix and ask_pipeworx family provide some consistency, but overall the style is not uniform.

Tool Count2/5

33 tools is a large number for the server's scope. While it covers many domains (data querying, entity research, Polymarket analysis, subscriptions, memory, utilities), there is redundancy: three ask_pipeworx variants and six Polymarket-specific tools inflate the count. Several tools could be merged or dropped without losing functionality, making the set feel heavier than necessary.

Completeness4/5

The toolset covers its core domains well: data querying (ask_pipeworx, deep_research), entity resolution (resolve_entity, entity_profile, compare_entities), Polymarket analysis (research, arbitrage, risk, edges, tracking, cross-venue), subscriptions (subscribe/unsubscribe/list/alerts), memory (remember/recall/forget), and utilities (MIME lookup, dependency scan). Minor gaps exist, such as no direct fetch tool for pipeworx:// citation URIs and no update operation for subscriptions, but these are not critical.

Resources