Skip to main content
Glama

Opensea

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, open-world, idempotent, and non-destructive behavior. The description adds valuable context beyond annotations: explains limits (60-day TTL, snapshot start), data frequency (daily closes, not intraday), and meaning of negative values in edge_pp_net.

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 dense and front-loads the core purpose. While it contains a lot of detail, each sentence provides useful information. Slightly verbose but justified.

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 is provided, so the description fully explains the return structure (tracked, expired, snapshot_dates) and their fields. It also covers parameter defaults and limits. The description is complete for the tool's complexity.

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 baseline is 3. The description repeats default and max for 'days' but does not add significant new meaning beyond what the input schema already provides.

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: providing edge persistence and decay telemetry from daily snapshots. It answers a specific question ('how long has this edge existed and is it shrinking?') and distinguishes itself from the sibling tool 'polymarket_edges' by focusing on time-series 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 gives context on when to use the tool (e.g., comparing fresh vs. aged edges) and explains the output structure. However, it does not explicitly state when not to use or mention alternative tools.

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

All Opensea 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.6/5.0
Disambiguation2/5

Tools cluster into overlapping groups: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are near-duplicates distinguished only by mode; bet_research, polymarket_edges, and polymarket_arbitrage all target prediction-market opportunities. The five OpenSea read tools are distinct, but they are buried among several unrelated domains, making misselection likely.

Naming Consistency4/5

Names are overwhelmingly snake_case with a verb_noun structure (get_collection, list_owned_nfts, validate_claim, create nothing but still remember/unsubscribe). Pipelined families like ask_pipeworx_* and polymarket_* are consistent, with only minor deviations such as pipworx_trending or bet_research not following a clear verb-object pattern.

Tool Count2/5

36 tools is too many for a coherent server, and the count is inflated by at least four unrelated domains: OpenSea NFT reads, Pipeworx data lookup/research, Polymarket betting, and memory/subscription utilities. Only five tools actually relate to the server's stated OpenSea purpose, so the surface is heavily bloated with off-scope functionality.

Completeness2/5

The OpenSea-relevant tools cover basic read operations—collections, stats, single NFT, collection NFTs, and owned NFTs—but omit search, events, offers/listings, order book data, and account/contract details. The many unrelated Pipeworx tools do not fill these gaps, so an agent needing real marketplace behavior would hit dead ends.

Resources