Skip to main content
Glama

uooks

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

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

The description goes well beyond the annotations (readOnlyHint, idempotentHint, destructiveHint) by disclosing data nuances: snapshots are cache-miss-driven so gaps mean no scan that day, the 60-day TTL bounds history depth, and decay numbers are computed from daily closes not intraday. It also clearly states the trend calculation is on |edge_pp_net| and signed values indicate trade direction, giving critical behavioral insight.

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?

The description is dense but every sentence earns its place. It front-loads the core purpose, then uses labeled sections 'Args:', 'RESPONSE:', and 'LIMITS:' to structure parameter, return, and constraint details efficiently. This makes it easy to scan and parse despite its length.

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?

With no output schema, the description fully explains the response structure: tracked[], expired[], and snapshot_dates[], including what each contains and why (e.g., median lifespan as a competition clock). It also notes limitations (TTL, cache-miss gaps, daily closes) that are critical for correct interpretation, making it 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.

Parameters3/5

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

Schema description coverage is 100%, so baseline is 3. The description restates parameters and their defaults ('days (lookback, default 14, max 30)', 'window (snapshot family, default "1wk")'), but does not add new semantics beyond what the schema already provides. It is consistent and correct, but not additive.

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 clearly states a specific verb+resource: it tracks edge persistence and decay from daily polymarket_edges snapshots. It answers a concrete question, 'how long has this edge existed and is it shrinking?', and differentiates itself from related tools like polymarket_edges by focusing on historical time-series rather than current values.

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?

The description provides clear context for when to use the tool: when assessing whether an edge is fresh or old ('a fresh wide edge and a 3-week-old wide edge are different trades'). It does not explicitly name sibling alternatives, but the 'built from daily polymarket_edges snapshots' phrasing implies it is the go-to for historical persistence analysis, which is sufficient contextual guidance.

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

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

Several tool families overlap at the boundaries: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all route questions to the same 5,724 tools, and ask_pipeworx_beta is currently functionally identical to ask_pipeworx. The Polymarket family is large but each member has a fairly distinct role (research vs. edge scan vs. fill risk vs. tracking); the memory trio and book tools are clear.

Naming Consistency3/5

Most tools follow a snake_case verb_noun pattern (get_book, create, search_books, resolve_entity, list_subscriptions), but there are notable exceptions: recall/remember/forget are bare verbs without a domain prefix, ask_pipeworx begins with a verb but doesn't follow the noun-object structure, and ai_visibility_check/generate_llms_txt break the pattern. It's readable and mostly predictable, but not uniform.

Tool Count3/5

35 tools is heavy and exceeds the typical well-scoped range, but the server is a meta-platform exposing a universal data router plus prediction-market analysis, book lookup, memory, subscriptions, and several composite research tools. Each tool appears to earn its place, though the set feels sprawling and would benefit from consolidation of the ask_pipeworx variants.

Completeness4/5

Coverage is thorough within the apparent domains: data lookup has multiple tiers (casual, grounded, deep research, claim validation), the Polymarket workflow is complete from research to edge discovery to fill-risk verification, memory has save/retrieve/delete, and subscriptions have create/list/cancel/pull. Minor gaps exist (e.g., book author search by name only via Open Library key, no direct tool for invoking a specific raw data pack), but nothing that would strand an agent.

Resources