Skip to main content
Glama

iconify

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

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

Even with readOnlyHint and idempotentHint annotations, the description adds substantial behavioral detail: the 60-day snapshot TTL, decay computed from daily closes net of slippage rather than intraday, snapshots only written on cache-miss, edge_pp_net being signed by trade direction, and the semantics of expired[] entries. This goes well 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 well-structured with labeled sections (Args, RESPONSE, LIMITS), and each sentence adds value. It is not lean, but the density is appropriate for a tool with such complex behavior and no output schema.

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 compensates thoroughly by enumerating response entries tracked[], expired[], snapshot_dates[] and explaining their fields and meanings. It also covers history depth and limitation context, making the tool's behavior predictable in context.

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 coverage is 100%, so the baseline is 3. The description restates days/window defaults and qualifies window as a 'snapshot family,' but it does not materially expand on schema details like the 2-30 clamp or the exact enum values.

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 names a specific resource: 'Edge persistence and decay telemetry built from daily polymarket_edges snapshots' and poses a targeted question, 'how long has this edge existed and is it shrinking?' It distinguishes itself from siblings like polymarket_edges by focusing on time-series persistence rather than current edge 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?

It clearly conveys when to use the tool: to understand edge history across daily snapshots, noting that a fresh wide edge and a 3-week-old wide edge are different trades. It also provides context on snapshot gaps and TTL limits, though it does not explicitly name alternative tools or state exclusions.

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

All iconify 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.6/5.0
Disambiguation1/5

Multiple tools have heavily overlapping purposes: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all route questions to the same data sources, and the Polymarket family (polymarket_edges, polymarket_edge_tracker, polymarket_arbitrage, polymarket_fill_risk, polymarket_kalshi_spread) has blurred boundaries. Agents would struggle to pick the right one without reading every description carefully.

Naming Consistency2/5

Naming is mostly snake_case but follows no consistent verb_noun pattern. Verbs vary widely (ask_, get_, list_, search_, compare_, scan_, validate_, remember, recall, forget, subscribe, unsubscribe, discover, generate, resolve, suggest) and many tools are bare nouns (entity_profile, recent_alerts, polymarket_edges). The inconsistency makes the set feel ad hoc.

Tool Count2/5

34 tools is on the heavy side, and the count is inflated by many near-duplicate data-router and prediction-market tools. The server is named 'iconify' yet only 3 of 34 tools actually relate to icons, indicating poor scoping for the stated purpose.

Completeness2/5

For the icon domain, the surface is minimal (list, search, get) with no create/update/delete. For the broader data/prediction-market domain, there are significant gaps in lifecycle coverage (e.g., subscriptions have create/cancel but no pause/resume, and the memory tools lack namespacing). The mixed focus means no single domain is fully covered.

Resources