Skip to main content
Glama

Myvariant

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

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

Annotations already indicate read-only, safe, idempotent behavior. The description adds rich behavioral details: response structure, time-series data, trend computation, source dependencies (snapshot TTL, daily closes), and limitations (no intraday).

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-structured with a concise summary followed by detailed response sections. While thorough, it is somewhat lengthy; each sentence earns its place but could be slightly more terse.

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?

For a tool with no output schema, the description fully explains the return values and fields. It covers all aspects needed for an agent to use it correctly, including edge cases like gaps in snapshots.

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%, so parameters are already documented. The description adds default values and usage context but does not significantly enhance meaning beyond the schema. Baseline applies.

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 as edge persistence and decay telemetry, using specific verbs and resources. It contrasts with sibling 'polymarket_edges' by focusing on time-series and decay metrics.

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 (distinguishing fresh vs. old edges) but does not explicitly state when not to use it or list alternatives. The context is clear, but exclusions are implied.

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

All Myvariant 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.9/5.0
Disambiguation2/5

Several clusters have overlapping purposes: ask_pipeworx and ask_pipeworx_beta are explicitly identical, and the five prediction-market tools (bet_research, polymarket_edges, polymarket_arbitrage, polymarket_kalshi_spread, polymarket_fill_risk) all target 'find edge in Polymarket markets' with subtle differences. query and variant both retrieve the same variant annotations, and ai_visibility_check vs scan_competitor_ai_presence are near-duplicates.

Naming Consistency4/5

Most tools follow a consistent verb_noun or domain-prefixed pattern (ask_pipeworx, compare_entities, resolve_entity, polymarket_edges, remember/recall/forget). Minor deviations exist: the bare nouns query, variant, and metadata are less descriptive, and ask_pipeworx_beta uses a suffix instead of a clean verb pattern, but the overall convention is fairly uniform.

Tool Count2/5

34 tools is far too many for a server named 'Myvariant' whose stated domain is genetic variant annotations. The set is a grab-bag spanning genetic data, Pipeworx query routing, Polymarket betting, memory persistence, subscriptions, AI visibility, and npm dependency scanning. Most tools are unrelated to the server's apparent purpose, making the count feel bloated and incoherent.

Completeness3/5

Individual clusters are reasonably complete: variants have search/get/metadata, memory has remember/recall/forget, and subscriptions have subscribe/list/unsubscribe/alerts. However, as a Myvariant server the surface is massively over-scoped yet oddly missing any batch-variant or annotation-source-specific lookup, and the sprawling multi-domain design makes 'complete' hard to meaningfully assess.

Resources