Skip to main content
Glama

Findymail

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. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations indicate readOnlyHint=true, openWorldHint=true, idempotentHint=true, destructiveHint=false. The description adds significant behavioral context: snapshots have a 60-day TTL, decay is computed from daily closes (not intraday), and gaps occur when no scan ran. No contradictions.

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 detailed and front-loaded with the key question. It could be slightly more concise, but every sentence adds value, especially for the output structure. The length is justified given the output schema absence.

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?

No output schema exists, so the description fully explains return values (tracked[], expired[], snapshot_dates[]) with field details and limitations (TTL, decay computation). It is comprehensive for a telemetry tool.

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%, with both parameters already described. The description adds minor context (e.g., default values and allowed values) but mostly repeats schema info. Baseline 3 is appropriate as schema does the heavy lifting.

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 clearly states the tool provides 'edge persistence and decay telemetry' answering the question of how long an edge has existed and whether it is shrinking. It specifies the resource (daily polymarket_edges snapshots) and distinguishes from sibling tools like polymarket_edges by focusing on time-series and decay.

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 gives clear context on when to use the tool: when you need to know if an edge is persistent or decaying, and contrasts fresh vs old edges. It implicitly guides usage by describing the output structure, though it does not explicitly state when not to use or list alternatives.

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

All Findymail 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.8/5.0
Disambiguation2/5

Several tools have heavily overlapping purposes: ask_pipeworx and ask_pipeworx_beta are currently identical, deep_research/validate_claim/ask_pipeworx all route factual questions to the same underlying catalog, and ai_visibility_check is essentially wrapped by scan_competitor_ai_presence. The long descriptions help, but the boundaries between query, research, and verification tools are genuinely ambiguous.

Naming Consistency2/5

Names are all lowercase snake_case, but there is no consistent verb_noun or domain pattern: ask_pipeworx, findymail_find_email, scan_competitor_ai_presence, polymarket_kalshi_spread, and generate_llms_txt each use a different structural convention. The mix of brand prefixes, domain prefixes, and bare commands makes the naming feel ad hoc rather than systematic.

Tool Count2/5

33 tools is well over the 25+ threshold and reflects a server that bundles at least five distinct concerns: email lookup, structured data research, prediction-market analysis, subscriptions, and memory. Most individual tools earn their place, but the count is too high for coherent tool selection in a single MCP server.

Completeness3/5

Coverage is broad and mostly self-sufficient for the Pipeworx data ecosystem: querying, deep research, entity resolution, comparisons, verification, subscriptions, memory, and one-off utilities are all present. There are notable gaps though—there is no tool to fetch a full record from a returned pipeworx:// citation URI, and the Findymail side is limited to find/reverse with no verification or bulk capability.

Resources