Skip to main content
Glama

Hunter

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.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 response structure (tracked, expired, snapshot_dates), data sources (daily closes, not intraday), TTL limits, and snapshot gaps. 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?

Front-loaded with purpose, but somewhat verbose in parenthetical details. Every sentence adds value, though a slightly tighter structure could improve conciseness.

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?

Exceptionally complete for a tool with no output schema. Covers all response fields, limitations (TTL, gaps), and edge cases. Sufficient for agent to understand expectations.

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%, but description enhances parameter meaning by explaining days as lookback with defaults and clamping, and window as snapshot family. Provides extra context beyond schema descriptions.

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?

Clearly states the tool provides edge persistence and decay telemetry from daily snapshots, answering a specific question. Distinguishes itself from 'polymarket_edges' by focusing on time-series tracking rather than current edges.

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?

Implies usage for assessing edge age and decay through context like 'a fresh wide edge and a 3-week-old wide edge are different trades', but lacks explicit when-to-use or when-not-to-use guidance compared to siblings.

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

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

Several tool clusters have genuinely blurry boundaries: ask_pipeworx, ask_pipeworx_beta (explicitly 'currently matches ask_pipeworx exactly'), ask_pipeworx_grounded, and deep_research all route questions to the same 5,743-tool catalog, and the six Polymarket tools (bet_research, polymarket_edges, polymarket_arbitrage, polymarket_edge_tracker, polymarket_fill_risk, polymarket_kalshi_spread) heavily overlap on 'should I bet / where is the edge'. The descriptions are detailed and cross-reference each other, but an agent would still struggle to pick correctly among near-duplicates.

Naming Consistency3/5

Everything is uniformly snake_case and readable, but there is no consistent verb_noun pattern: verb_noun (resolve_entity, discover_tools, validate_claim) mixes with noun_noun (domain_search, entity_profile, polymarket_arbitrage), adjective_noun (deep_research, recent_changes), bare verbs (forget, recall, remember), and brand prefixes (pipeworx_*, ask_pipeworx_*). Readable, but patternless.

Tool Count2/5

34 tools is well above the heavy threshold, but the bigger issue is scope incoherence: a server named 'Hunter' dedicates only 3 of 34 tools to Hunter.io email lookup while the remaining 31 belong to an unrelated Pipeworx data-research/prediction-market platform. The count is not earned by a single coherent purpose.

Completeness3/5

The Pipeworx research core is quite thorough: entity resolution, single-lookup, grounded answers, deep research, profiles, comparisons, claim validation, semantic search-within-records, change feeds, subscriptions, and memory form a full research lifecycle. However, the domain is a grab-bag spanning email finding, npm dependency checking, prediction markets, and data research, and the three Hunter.io tools that match the server name are only a thin fragment of the surface.

Resources