Skip to main content
Glama

Mesh

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

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

Annotations indicate readOnly, openWorld, idempotent, non-destructive. Description adds detail about snapshot TTL (60 days), cache-miss-based snapshot creation, and decay calculation from daily closes, providing useful behavioral context 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?

Well-structured with sections for Args, RESPONSE, LIMITS. Front-loaded with purpose. Slightly verbose but every sentence contributes meaningful information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite missing output schema, the description thoroughly explains the response fields (tracked, expired, snapshot_dates) and their semantics. Covers limitations like TTL and data gaps. Could mention error handling or parameter validation briefly.

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?

Both parameters are documented in schema (100% coverage). Description adds context on defaults (14 days, '1wk'), constraints (max 30), and explains how they affect the response (lookback, snapshot family). Also describes response structure that relies on parameters.

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 states it provides edge persistence and decay telemetry from daily snapshots. Answers the specific question about edge longevity. Differentiates from sibling polymarket_edges by focusing on time-series and decay.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implies usage context (comparing fresh vs old edges) but does not explicitly state when to use this tool versus sibling polymarket_edges or when not to use it.

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

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

The three ask_pipeworx variants are a genuine confusion risk — ask_pipeworx_beta is currently described as identical to ask_pipeworx, and ask_pipeworx_grounded differs only in extraction strictness. search_descriptors and resolve_term also overlap heavily (both map a term to MeSH descriptor IDs). The six Polymarket tools are differentiated by rich descriptions but still form a dense cluster where misselection is plausible.

Naming Consistency4/5

Most tools follow a clean verb_qualifier pattern (ask_, bet_, compare_, resolve_, search_, validate_) with the brand as a namespace (ask_pipeworx, pipeworx_trending, polymarket_*). Minor deviations exist: pipeworx_feedback and pipeworx_trending lead with a noun, the memory trio (remember, recall, forget) are bare verbs, and the ask_pipeworx family uses a brand name rather than a resource noun — but the overall pattern stays predictable and readable.

Tool Count2/5

At 34 tools this exceeds the threshold where a set feels heavy, and the bloat is visible: three near-identical ask_pipeworx routers and a six-tool Polymarket suite dominate. Several tools (generate_llms_txt, scan_dependency, bet_research) feel like accreted one-offs rather than part of a coherent surface. The broad platform purpose justifies some breadth, but the count is inflated by redundant variants.

Completeness4/5

The core purpose — universal access to authoritative structured data — is well covered via the router, grounded mode, deep_research, entity/profile/compare/validate wrappers, and discovery tools. The subscription lifecycle (subscribe/unsubscribe/list/alerts) and memory (remember/recall/forget) have no dead ends. Minor gaps exist: non-polymarket prediction-market workflows lack the depth of the Polymarket cluster, and the single-purpose niche tools fit awkwardly, but agents won't hit dead ends.

Resources