Skip to main content
Glama

Horizons Nasa

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

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

Annotations indicate readOnlyHint, idempotentHint, and non-destructive. The description adds critical context: history bounded by 60-day TTL, decay based on daily closes (not intraday), and gaps when no data scanned. 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 well-organized with clear sections (purpose, args, response, limits), but somewhat verbose. Every sentence adds value; front-loads the core question.

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, but the description fully defines response fields (tracked, expired, snapshot_dates) and edge cases (gaps, TTL, signed decay). Complete for a read-only 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% with descriptions. The description reinforces defaults and limits (days default 14 max 30, window default '1wk') and clarifies that 'window' is a snapshot family. Adds value over schema.

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: edge persistence and decay telemetry from daily snapshots, answering 'how long has this edge existed and is it shrinking?' It contrasts with sibling polymarket_edges by focusing on historical trends 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?

The description explains when to use the tool (to distinguish fresh edges from old ones) and implicitly contrasts with polymarket_edges. However, it does not explicitly list when not to use it or provide alternative tools for other scenarios.

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

All Horizons Nasa 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

A4/5.0
Disambiguation5/5

Each tool has a clear, distinct purpose with detailed descriptions that differentiate overlapping capabilities (e.g., ask_pipeworx vs deep_research vs ask_pipeworx_grounded vs bet_research). No two tools appear redundant; even similar prediction-market tools (polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker, polymarket_fill_risk) have specific scopes.

Naming Consistency5/5

Tool names consistently use lowercase snake_case (e.g., ai_visibility_check, compare_entities, pipeworx_trending, polymarket_kalshi_spread). Single-word exceptions (ephemeris, lookup, observers, recall, remember, vectors) are common short verbs and do not break the pattern. No mixing of camelCase or other conventions.

Tool Count4/5

35 tools is above the typical 3-15 range, but the server is a comprehensive data platform covering multiple domains (SEC, FDA, FRED, prediction markets, memory, subscriptions, feedback). The count is justified given the breadth; it feels slightly heavy but not bloated or redundant.

Completeness5/5

The tool surface covers the full lifecycle for a data/research platform: discovery (discover_tools, suggest_questions), entity resolution (resolve_entity), lookups (ask_pipeworx, entity_profile), comparison (compare_entities), validation (validate_claim), prediction-market operations (polymarket_*), memory (remember/recall/forget), subscriptions (subscribe/unsubscribe/list_subscriptions/recent_alerts), and meta/feedback (pipeworx_feedback, pipeworx_trending). No obvious gaps for typical workflows.

Resources