Skip to main content
Glama

Gets Nz

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

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

Beyond the annotations (readOnlyHint, etc.), the description discloses many behavioral traits: snapshots are written on cache-miss, gaps mean no scan, output includes tracked/expired/snapshot_dates, decay computed from daily closes, and 60-day TTL. This adds significant context beyond what annotations provide.

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 but front-loaded with the purpose. It is structured with arguments, response format, and limits. While every sentence adds value, it is somewhat dense and could be more concise, but given the complexity, it is well-organized.

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?

Without an output schema, the description fully explains the return format: tracked[] with full time-series, trend, decay; expired[] with lifespan; snapshot_dates[]. It also covers limits like 60-day TTL and data gaps. Complete for a telemetry tool.

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%, so baseline is 3. The description adds meaning by explaining the purpose of 'days' (lookback) and 'window' (snapshot family), and how snapshots are written on cache-miss. This goes beyond the schema's simple field 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?

The description clearly states the tool's purpose: tracking edge persistence and decay from daily snapshots. It uses a specific verb ('telemetry built from') and resource ('polymarket_edges snapshots'), and implicitly distinguishes from the sibling 'polymarket_edges' tool by focusing on historical analysis.

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 provides a clear use case: answering 'how long has this edge existed and is it shrinking?'. It explains the output structure and limits, but does not explicitly state when not to use or compare with alternatives. The context implies usage for historical telemetry vs. raw edges, but lacks explicit exclusions.

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

All Gets Nz 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

Multiple tools overlap significantly: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded serve nearly identical purposes, and deep_research further duplicates. Polymarket tools (bet_research, polymarket_arbitrage, polymarket_edges, etc.) also have overlapping scopes, making it hard for an agent to select the correct one without deep inspection.

Naming Consistency3/5

Tool names use a mix of patterns: some are descriptive phrases (ai_visibility_check, generate_llms_txt), others are domain-prefixed (nz_tender_*, polymarket_*) but lack a uniform verb_noun structure. The ask_pipeworx series diverges from the rest, and verb choices are inconsistent (compare_entities vs scan_competitor_ai_presence).

Tool Count2/5

With 34 tools, the surface is large and feels bloated. The server covers multiple distinct domains (NZ tenders, Polymarket, memory, subscriptions) that could be separate servers. Many tools are variants of the same core functionality (e.g., four ask_pipeworx variants), inflating the count without clear necessity.

Completeness3/5

For a general-purpose data query server, the tool set covers a broad range of sources (SEC, FDA, FRED, etc.) and includes CRUD for memory and subscriptions. However, obvious gaps exist: no dedicated web search tool (ask_pipeworx is for structured data), and NZ coverage is limited to tenders only. Missing update/delete for some resources (e.g., no way to modify a subscription beyond unsubscribe).

Resources