Skip to main content
Glama

Gnomad

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

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds critical behavioral context: snapshots are written only on cache-miss, gaps imply no scan that day, 60-day TTL limits history, decay is computed on daily closes net of slippage, and expired opportunities have lifespan data. This far exceeds annotation coverage.

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?

While dense, the description is well-structured into ARGS/RESPONSE/LIMITS sections and front-loads the core value proposition. Every sentence adds specific information — no filler.

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 compensates by detailing the exact response shape: tracked[] with edge_pp_net time-series, trend, decay per day; expired[] with lifespan_days; snapshot_dates[]. It also states history limits and data-generation conditions, making the tool fully understandable.

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 covers both parameters fully (100%). Description adds clarity that `days` is the lookback (default 14, max 30) and `window` selects the snapshot family (default 1wk), complementing the schema's clamp/default details.

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?

Description explicitly states 'Edge persistence and decay telemetry built from daily polymarket_edges snapshots' and poses the core question it answers ('how long has this edge existed and is it shrinking?'). This clearly differentiates from sibling tools like polymarket_edges (which likely provides current edges) and polymarket_arbitrage.

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 implies usage by explaining that edge age changes trade interpretation ('a fresh wide edge and a 3-week-old wide edge are different trades'). It provides defaults and limits but does not explicitly name alternatives or when-not-to-use scenarios.

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

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

The set mixes several overlapping query surfaces: ask_pipeworx and ask_pipeworx_beta are currently identical, ask_pipeworx_grounded/deep_research/discover_tools/suggest_questions all serve related retrieval/discovery purposes, and the five polymarket_* tools have similar opportunity-finding goals. Only the unusually detailed descriptions save some tools from misselection; an agent would struggle to quickly pick the right one.

Naming Consistency4/5

Names are uniformly snake_case and mostly follow a verb_noun or prefixed_noun pattern (ask_pipeworx, validate_claim, polymarket_edges, scan_dependency). Minor inconsistencies exist — bare nouns like gene/variant/search sit alongside compound names like generate_llms_txt, and the pipeworx_ prefix isn't applied to ask_pipeworx/deep_research — but the overall style is recognizable and predictable.

Tool Count2/5

36 tools is too many for a coherent server, especially since the domains are largely unrelated: 5 gnomAD genomics tools, 20+ Pipeworx/Polymarket data tools, memory CRUD, subscription management, and a couple of web-dev utilities. The count doesn't align with a single obvious scope and would overwhelm an agent selecting among them.

Completeness3/5

Within the major subdomains coverage is strong: memory has remember/recall/forget, subscriptions have full lifecycle tools, and Polymarket has edge detection plus fill-risk checking. However, there are notable gaps — no tool to fetch a pipeworx:// citation URI despite deep_research promising resolvable citations, and the gnomAD surface lacks batch queries, coverage, or constraint data for a server named Gnomad.

Resources