Skip to main content
Glama

Spdx License

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

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds substantial behavioral context: response structure, snapshot TTL limits, cache-miss snapshotting, the signed edge_pp_net convention, and the daily-close basis for decay. This exceeds annotation coverage and clarifies edge cases.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long but efficiently organized into sections: purpose, args, response, limits. Each sentence carries distinct information, and the use of ALL-CAPS section headers front-loads the key details. The length is justified by the tool's complexity.

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?

There is no output schema, but the description fully documents the return value (tracked[], expired[], snapshot_dates[]) including field semantics and edge cases. Limits and data-availability quirks (TTL, gaps) are disclosed, making the description self-sufficient for understanding the tool's behavior.

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%, with both parameters described in detail (defaults and clamps). The description repeats the parameter defaults and adds the 'snapshot family' interpretation of window, but this is also in the schema. No major new semantics are added beyond the schema, so the baseline 3 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 opens with a specific verb phrase 'Edge persistence and decay telemetry built from daily polymarket_edges snapshots' and states the core question it answers ('how long has this edge existed and is it shrinking?'). This distinguishes it from sibling tools like polymarket_edges, which likely provides current edge data rather than historical persistence 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 explains when to use the tool via the contrast between 'a fresh wide edge and a 3-week-old wide edge' and notes 'the median lifespan is your competition clock.' It implicitly positions itself against polymarket_edges by stating it is built from those snapshots, though it doesn't explicitly name a preferred alternative. Clear context with no exclusions warrants a 4.

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

All Spdx License 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

Many tools have overlapping purposes, such as multiple 'ask_pipeworx' variants, several company analysis tools, and multiple prediction market tools. The set is large and not well-disambiguated, leading to potential confusion.

Naming Consistency2/5

Naming conventions are mixed, with snake_case ('get_license'), camelCase ('ai_visibility_check'), and prefix-based ('pipeworx_*', 'polymarket_*'). No consistent pattern across the tool set.

Tool Count2/5

35 tools is excessive for a server named 'Spdx License', which implies a focused license management tool. The actual number is more appropriate for a general data platform, but mismatched with the server name.

Completeness1/5

For the implied SPDX license domain, only a few basic tools exist (list, get, search). Missing crucial features like create, update, delete, or compare licenses. The surface is severely incomplete for the stated purpose.

Resources