Skip to main content
Glama

emojihub

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

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

Beyond the readOnly/idempotent annotations, the description richly details behavior: the tracked/expired/snapshot_dates response structure, signed edge_pp_net meaning, 60-day TTL bound, cache-miss snapshot writing, and daily-close decay calculation. 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is organized into purpose, Args, RESPONSE, and LIMITS sections, with the core purpose front-loaded in the first sentence. Every sentence carries essential information; there is no filler or redundancy despite the length, making it efficiently structured.

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 documents return shape (tracked, expired, snapshot_dates) and limitations (TTL, snapshot gaps, daily-close basis). For a 2-param read-only telemetry tool, this is comprehensively 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% (both params described), so baseline is 3. The description adds value by stating defaults/clamps (days default 14, max 30), explaining window as 'snapshot family' (24hr/1wk/1mo), and grounding both in the response semantics. This exceeds schema basics but isn't dramatic.

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 'Edge persistence and decay telemetry built from daily polymarket_edges snapshots' – a specific verb+resource+scope. It clearly answers 'how long has this edge existed and is it shrinking?' and distinguishes itself from sibling polymarket_edges by focusing on temporal 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?

The description clearly implies when to use it: for assessing edge endurance and decay, contrasting fresh vs. old wide edges. It gives context but does not explicitly name alternatives or say 'use this instead of X', so it lacks explicit exclusion guidance. This is clear context without alternatives, earning a 4.

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

All emojihub 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
Disambiguation4/5

Most tools have clearly distinct purposes, but there is some overlap among the numerous Pipeworx query and prediction market tools (e.g., polymarket_arbitrage vs. polymarket_edges vs. polymarket_fill_risk). Descriptions help differentiate them, so the ambiguity is minor.

Naming Consistency3/5

Tool names use a mix of verb_noun patterns (e.g., list_subscriptions, validate_claim), phrases (ask_pipeworx, bet_research), and standalone nouns (pipeworx_feedback). While readable, the lack of a single consistent convention makes the set feel less cohesive.

Tool Count3/5

33 tools is on the high side, with many highly specialized prediction market and Pipeworx management tools. The server's name 'emojihub' suggests a narrow focus, but the actual scope is much broader, making the count feel somewhat inflated for its apparent purpose.

Completeness4/5

The tool set covers a vast domain: factual data retrieval, company profiles, comparisons, claim validation, prediction market analysis, memory, subscriptions, and emoji lookup. Minor gaps exist (e.g., no direct tool for simple web search), but overall coverage is comprehensive.

Resources