Skip to main content
Glama

Caniuse

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).

TDQS

A4.4/5.0
Behavior5/5

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

Exceeds the annotations by detailing the response structure (tracked[], expired[], snapshot_dates[]), explaining what each field represents (e.g., 'trend (new | widening | stable | decaying)'), and disclosing limitations: 'history depth is bounded by the 60-day snapshot TTL', 'decay numbers come from daily closes of edge_pp_net... not intraday', and notes about snapshot gaps. This is rich behavioral context beyond read-only/idempotent hints.

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?

The description is long but well-structured with clear sections (Args, RESPONSE, LIMITS). It front-loads the core purpose and then details outputs and limitations. Every sentence contributes meaning, but the purpose phrase 'a fresh wide edge and a 3-week-old wide edge are different trades' is slightly verbose. Overall efficient for the tool's complexity.

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?

Given no output schema, the description fully explains the response format (tracked, expired, snapshot_dates), field semantics, and limitations (TTL, daily closes). It covers prerequisites (snapshots from polymarket_edges), data gaps, and how to interpret results. This is comprehensive for a 2-parameter tool with no output schema.

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?

Input schema covers 100% of the parameters with descriptions, so a baseline of 3 is appropriate. The description repeats parameter info ('Args: days (lookback, default 14, max 30), window (snapshot family, default "1wk")') but adds no new semantics beyond the schema. It aligns with the schema's 'clamp 2-30' and window enum values, so no gaps but also no added value.

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 opens with a specific purpose: 'Edge persistence and decay telemetry built from daily polymarket_edges snapshots.' It clearly answers the question 'how long has this edge existed and is it shrinking?' differentiating it from sibling tools like polymarket_edges (current edges) by focusing on historical persistence and decay. The verb and resource are specific and unambiguous.

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 clear context for when to use: 'a fresh wide edge and a 3-week-old wide edge are different trades' — this implies using the tool to assess edge aging. However, it does not explicitly name alternatives or state when not to use, though the sibling context and phrasing imply it complements polymarket_edges. The guidance is sufficient but lacks explicit exclusions.

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

All Caniuse 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.9/5.0
Disambiguation2/5

The tool set has significant overlap: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are near-identical variants, and deep_research, entity_profile, compare_entities, recent_changes, and validate_claim all retrieve structured data with overlapping capabilities. The five Polymarket-oriented tools (bet_research, polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker, polymarket_fill_risk, polymarket_kalshi_spread) further blur boundaries. Agents will struggle to select the right tool without reading very long descriptions.

Naming Consistency4/5

Most tools follow a clear snake_case verb_noun pattern (ask_pipeworx, compare_entities, validate_claim), and the polymarket_* cluster is consistently prefixed. However, a few tools are bare nouns (feature, support, search) and the remember/forget/recall trio deviates from the dominant pattern, creating minor inconsistency.

Tool Count2/5

35 tools is excessive for a server named 'Caniuse' — only 4 tools actually pertain to browser compatibility (feature, support, search, list_browsers), while 31 are Pipeworx data tools. The server name misrepresents the content, and the sheer number overwhelms rather than scopes the surface.

Completeness3/5

For the caniuse domain, coverage is complete (search, feature, support, list_browsers). The Pipeworx side includes meta-tools (discover_tools, suggest_questions), retrieval, memory, subscriptions, and feedback, but some tools require accounts and there are gaps like no direct way to list all data sources without discover_tools. The overall surface is broad but lacks obvious missing operations for any single coherent domain.

Resources