Skip to main content
Glama

Ulid

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

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

Adds significant behavioral context beyond annotations: explains snapshot triggers, gaps meaning, decay computation from daily closes, and response structure. No contradiction with 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 purpose first, then response explanation, then limits. Somewhat long but every sentence adds value. Front-loaded with the key question.

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?

Thoroughly explains response fields (tracked, expired, snapshot_dates) despite no output schema, covering all relevant aspects and limits. Very complete for a low-complexity tool.

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?

Description adds default values and constraints (days default 14, max 30; window default '1wk') beyond the schema. Schema coverage is 100%, so description adds useful usage context.

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?

Description clearly states it provides edge persistence and decay telemetry from daily snapshots, answering specific questions about edge age and trend. It distinguishes from siblings like polymarket_edges by focusing on historical time-series.

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?

Description gives clear context on when to use (e.g., comparing fresh vs old edges) and mentions limits (history depth, TTL, no intraday). However, it does not explicitly state when NOT to use or name alternatives.

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

All Ulid 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
Disambiguation2/5

Several tool clusters overlap heavily: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all serve as query entry points (with ask_pipeworx_beta explicitly identical to ask_pipeworx right now); polymarket_edges, polymarket_edge_tracker, polymarket_arbitrage, polymarket_fill_risk, polymarket_kalshi_spread, and bet_research form a dense prediction-market suite; ai_visibility_check and scan_competitor_ai_presence are single vs. multi variants. An agent would frequently struggle to pick the right tool without reading long descriptions.

Naming Consistency4/5

Most tools follow a clean snake_case convention and are mostly verb_noun (generate_ulid, parse_ulid, list_subscriptions, resolve_entity, validate_claim, compare_entities), making the set predictable. Minor deviations exist (entity_profile, deep_research, bet_research, ask_pipeworx_beta) but they are still readable and don't break the overall pattern.

Tool Count2/5

33 tools is well above the 25-tool threshold for a heavy surface, and the server name 'Ulid' suggests a tiny scope that wildly mismatches the actual content. While the real domain (Pipeworx data + prediction markets) is broad, the set bundles many subdomains into one server, making navigation and selection costly.

Completeness4/5

For the actual apparent domain—structured data research, entity lookups, verification, prediction-market analysis, memory, and subscriptions—coverage is strong: query, grounded query, deep research, entity profiles, comparisons, resolution, validation, discovery, alerts, and memory tools are all present. ULID functionality is minimal but sufficient (generate + parse). Minor gaps exist (e.g., no direct single-source browser beyond discover_tools) but agents can work around them.

Resources