Skip to main content
Glama

deckofcards

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

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

Even though annotations already indicate read-only, idempotent, and non-destructive behavior, the description adds substantial context: response structure, edge trend classification, decay calculation methodology, snapshot date gaps, and TTL boundaries. It also discloses that decay numbers are from daily closes, not intraday, which is valuable behavioral nuance beyond the 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?

The description is long but highly structured, with sections for overview, arguments, response fields, and limits. Each sentence adds unique value—no filler. The length is justified by the absence of an output schema, meaning the description must carry the full weight of documenting the response format. The organization makes it scannable despite the detail.

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 thoroughly documents the return structure: tracked[], expired[], and snapshot_dates[], including what each field means. It also explains edge cases (gaps, TTL, cache-miss behavior) and computation details. For a tool with this complexity, the description is complete and leaves no major ambiguity.

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?

Schema coverage is 100% with both parameters described, so baseline is 3. The description goes further by explaining that 'window' selects a snapshot family and that 'days' is a lookback with a default. It also gives context about how snapshot dates relate to cache-miss behavior, adding meaning beyond the raw schema definitions.

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 verb+resource: 'Edge persistence and decay telemetry built from daily polymarket_edges snapshots.' It clearly distinguishes itself from sibling tools like polymarket_edges (current edges) by focusing on historical persistence and decay. The question it answers ('how long has this edge existed and is it shrinking?') is 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 Guidelines5/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 by explaining the trade insight: a fresh wide edge differs from a 3-week-old wide edge. It mentions the underlying source (polymarket_edges snapshots), implicitly framing it as the historical companion. The LIMITS section further sets expectations about data availability and computation, guiding appropriate usage.

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

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

B3.4/5.0
Disambiguation2/5

Multiple tools have overlapping purposes: ask_pipeworx and ask_pipeworx_beta are functionally identical (beta just has experimental routing), and the Polymarket suite (bet_research, polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker, polymarket_fill_risk, polymarket_kalshi_spread) all revolve around prediction-market signal detection with unclear boundaries. Also ai_visibility_check and scan_competitor_ai_presence overlap heavily.

Naming Consistency2/5

Naming is a mix of verb-first (draw_cards, resolve_entity, discover_tools) and noun-first (entity_profile, new_deck, recent_alerts) styles, with inconsistent prefixes (pipeworx_feedback vs ask_pipeworx) and no unifying convention. Some tools are bare verbs (recall, remember), others are noun phrases (polymarket_edges).

Tool Count2/5

34 tools is excessive for a server named 'deckofcards' — only 3 tools relate to cards. Even as a general-purpose data/research server, 34 is on the high end and includes many near-duplicates (ask_pipeworx variants) and highly specialized tools that could be consolidated.

Completeness3/5

The research side is fairly complete (lookup, grounding, comparison, profiles, claim verification, memory, subscriptions), but the card-deck functionality is minimal (only create, draw, shuffle) and lacks any deck inspection or hand management. The server's scope is unclear, making it hard to assess true coverage.

Resources