Skip to main content
Glama

Themeparks

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

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

Annotations already indicate read-only and idempotent. The description adds beyond: explains snapshot-based data, 60-day TTL, limitation of daily closes (not intraday), and structure of response fields like first_seen, trend, decay_pp_per_day. No contradictions.

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 somewhat long but efficiently structured: starts with core purpose, then detailed response format, then limits. Almost every sentence adds value, though minor redundancy could be trimmed.

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?

Despite no output schema, the description fully explains return structure (tracked[], expired[], snapshot_dates[]) with field semantics. Parameters are thoroughly described. Covers all necessary details for correct usage.

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 coverage is 100%, baseline 3. The description adds context: explains 'days' as lookback with default/max beyond schema constraints, and describes 'window' as snapshot family with examples. This provides useful additional meaning.

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' and answers a specific question about edge longevity. It distinguishes from sibling tool 'polymarket_edges' by focusing on historical trends rather than current values.

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 (analyzing edge history/decay) and contrasts fresh vs. aged edges. However, it lacks explicit instructions on when not to use or direct alternatives beyond the implied sibling tool.

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

All Themeparks 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
Disambiguation3/5

Most tools have distinct, well-documented purposes, but several overlap or are explicitly redundant: ask_pipeworx_beta currently behaves identically to ask_pipeworx, discover_tools and suggest_questions both serve as discovery entry points, and scan_competitor_ai_presence wraps ai_visibility_check. The thematic split between theme-park, data-lookup, prediction-market, and memory tools also forces agents to navigate unrelated clusters.

Naming Consistency3/5

Naming is a mix of verb_noun (list_destinations, get_wait_times, remember, resolve_entity), noun_phrase (entity_profile, recent_changes, bet_research), and brand-prefixed nouns (polymarket_edges, pipeworx_trending). Within families the patterns are consistent, but across the set the conventions are inconsistent and sometimes reverse the verb/noun order, making the surface harder to predict.

Tool Count2/5

35 tools is heavy, and the server is named Themeparks yet only 4 tools actually relate to theme parks. The remaining 31 tools span Pipeworx data retrieval, prediction markets, memory, subscriptions, and feedback, creating a bloated and misaligned scope. A tightly scoped theme-park server would need far fewer tools, and a general data research server would not be named Themeparks.

Completeness2/5

For the implied theme-park domain, the surface is thin: list destinations, get entity metadata, get schedule, and get wait times cover basic lookups but omit search, attraction details beyond waits, historical data, pricing, dining/show info, and park updates. The non-theme-park tools are extensive, but they do not complete the server's apparent stated purpose.

Resources