Skip to main content
Glama

Bart

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. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations indicate read-only, idempotent, and non-destructive behavior. The description adds significant context: response structure (tracked, expired, snapshot_dates), what decay numbers represent (daily closes, not intraday), and limitations (history bound by 60-day TTL, from snapshot enablement). 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 information-dense but efficiently structured, starting with purpose and then providing details on parameters, response, and limitations. It could be slightly more concise, but every sentence adds value.

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?

Given no output schema, the description fully explains the response structure and fields. It covers purpose, parameters, usage context, limitations, and behavioral details. Complete for a telemetry tool with simple parameters.

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 already covers both parameters with descriptions. The description adds context: 'days' is lookback with max 30 (schema says clamp 2-30), 'window' is snapshot family. It explains that snapshots are written on cache-miss, adding meaning beyond 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 the tool's purpose: providing edge persistence and decay telemetry from daily snapshots. It answers a specific question about edge longevity and distinguishes from sibling tools like polymarket_edges which likely just lists current edges.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives context that a fresh wide edge differs from an older one, implying when to use this tool to evaluate edge age. However, it does not explicitly state when to use this tool versus alternatives like polymarket_edges or polymarket_arbitrage, nor does it provide exclusions.

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

All Bart 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

A4/5.0
Disambiguation4/5

Most tools have clearly distinct purposes, but the three ask_pipeworx variants (stable, beta, grounded) overlap significantly in functionality, as do the Polymarket tools (bet_research, arbitrage, edges, etc.), which could cause an agent to misselect without careful reading of descriptions.

Naming Consistency3/5

Naming follows multiple styles: verb_noun (ask_pipeworx, compare_entities), domain first (polymarket_arbitrage, bart_departures), and single words (remember, forget). There is no consistent pattern, making the set feel disjointed.

Tool Count3/5

35 tools is on the heavy side for a single server. While each tool has a defined role, the count suggests potential for consolidation (e.g., merging ask_pipeworx variants or Polymarket tools). The server's broad scope partially justifies the count.

Completeness4/5

The tool surface covers a wide range of functionalities: structured querying, entity lookup, comparison, fact-checking, subscription management, memory, and domain-specific tools for BART and Polymarket. Minor gaps exist (e.g., no direct API for some data sources), but overall it feels comprehensive.

Resources