Skip to main content
Glama

Setlist Fm

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

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

Exceeds annotations by detailing data limits (60-day TTL, daily closes), response structure (tracked, expired, snapshot_dates), and edge sign convention (negative = SELL YES). 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.

Conciseness5/5

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

Front-loaded with core purpose, then logically details response structure and limitations. Every sentence contributes necessary context for a complex tool.

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?

Fully explains output format (tracked, expired, snapshot_dates with key fields) and data limitations (TTL, daily closes, gaps). No output schema exists, so description carries full burden and meets it.

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 description adds minimal extra value beyond defaults and clamping range. Parameters are adequately described in schema, meeting baseline.

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?

Clearly states it provides telemetry on edge persistence and decay, differentiating from siblings like polymarket_edges by focusing on historical evolution rather than current snapshots. The description explicitly contrasts fresh vs. old 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?

Implies usage for edge persistence analysis by asking 'How long has this edge existed and is it shrinking?' but does not explicitly exclude alternatives. Sibling tools listed provide context for differentiation.

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

All Setlist Fm 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

The tool set mixes two completely different domains: setlist.fm (12 tools) and Pipeworx data services (30+ tools). An agent cannot easily distinguish which tools belong to the server's primary purpose, leading to confusion and misselection.

Naming Consistency2/5

Setlist.fm tools use consistent verb_noun patterns (artist, artist_search, artist_setlists), but the majority of tools follow no unified convention: some use snake_case (ai_visibility_check), others use mixed case (ask_pipeworx), creating an inconsistent naming landscape.

Tool Count2/5

43 tools is excessive for a setlist.fm API. Only about 12 are relevant; the remaining 31 are unrelated and bloat the tool surface, making it hard to navigate and maintain.

Completeness4/5

For the setlist.fm domain, the tools cover search, retrieval, and user data comprehensively (artists, setlists, venues, cities, countries, users). Minor gaps exist (e.g., no update/delete operations), but core workflows are supported.

Resources