Skip to main content
Glama

Solscan

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 already provide readOnlyHint, openWorldHint, idempotentHint, destructiveHint. Description adds rich context: return fields (tracked, expired, snapshot_dates), trend computation, decay calculation, data gaps, and limits (60-day TTL). No contradiction with annotations.

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 well-structured: purpose first, then Args, then RESPONSE in caps. It is slightly verbose but every sentence adds value. Front-loads key information.

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, so description must explain return values. It does thoroughly: tracked[], expired[], snapshot_dates[], with explanations of each field (trend, decay, lifespan). Covers edge cases like gaps and limits.

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 description coverage is 100%. The description adds context: default values for days (14) and window (1wk), clamp range for days (2-30), and explains window as 'snapshot family.' This adds meaning beyond the 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 it provides 'edge persistence and decay telemetry' from daily snapshots, answering a specific question about edge longevity. It distinguishes itself from siblings like 'polymarket_edges' (which likely gives current edges) by focusing on historical trends.

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 when to use: when you need to know 'how long has this edge existed and is it shrinking?' It contrasts a fresh wide edge with an old one, but doesn't explicitly say when not to use it or name alternatives.

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

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

Several tools are near-duplicates: ask_pipeworx_beta is explicitly described as currently identical to ask_pipeworx, and multiple prediction-market tools (bet_research, polymarket_edges, polymarket_arbitrage) overlap in purpose. The Solana-specific tools are distinct, but the large non-Solana cluster creates real ambiguity.

Naming Consistency3/5

All tools use snake_case, but naming styles vary widely: get_/list_ verbs, ask_pipeworx family, polymarket_* cluster, and descriptive noun-style names like entity_profile, validate_claim, generate_llms_txt, scan_dependency. There is no single consistent verb_noun convention across the set.

Tool Count1/5

With 36 tools, the count is high, but the critical problem is scope mismatch: a server named Solscan has only 5 Solana-related tools, while 31 are unrelated data/research/prediction-market utilities. This makes the tool count inappropriate for the apparent purpose.

Completeness2/5

As a Solana explorer, the set covers only account details, token holdings, token metadata, transactions, and transfers; major gaps include blocks, token price/history, NFTs, programs/staking, and more comprehensive transfer history. For the broader data-research theme, coverage is broad but scattered and lacks a single coherent domain.

Resources