Skip to main content
Glama

Mbta

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

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

Adds extensive detail beyond annotations: response structure, decay computation, sign conventions, limitations (60-day TTL, snapshot gaps). 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?

Front-loaded with purpose, then details, then limitations. Somewhat verbose but each sentence adds value. Could be slightly more compressed.

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 describes response fields, parameter behavior, and limitations. No output schema, but the description compensates. Complete for this medium-complexity tool.

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 parameters with descriptions. The description reinforces defaults and ranges (lookback 14, max 30; window default '1wk'), adding minor value 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?

Clearly states the tool provides edge persistence and decay telemetry, distinguishing it from siblings like polymarket_edges and polymarket_arbitrage. Answers a specific question about edge freshness.

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?

Describes when to use the tool (to assess edge age and decay) and implies alternatives (e.g., polymarket_edges for current snapshot). Could explicitly state when not to use.

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

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

ask_pipeworx_beta is explicitly stated to be currently identical to ask_pipeworx, which is a direct duplication. The polymarket cluster (bet_research, polymarket_edges, polymarket_arbitrage, polymarket_fill_risk, polymarket_edge_tracker, polymarket_kalshi_spread) has heavily overlapping purposes around finding and validating betting edges, and the ask_pipeworx / ask_pipeworx_grounded / deep_research / validate_claim tools all handle natural-language 'look up X' queries, making misselection likely without reading lengthy descriptions.

Naming Consistency4/5

snake_case is uniform and helpful prefixes (mbta_, polymarket_, pipeworx_, ask_pipeworx) create recognizable families. However, verb style is inconsistent — imperative verbs like ask/compare/discover/validate mix with noun-first names like bet_research, entity_profile, and search_within, and the memory trio (remember/recall/forget) doesn't share a common prefix.

Tool Count2/5

At 35 tools this exceeds the comfortable range, and the count is inflated by near-duplicates (ask_pipeworx_beta) and a dense 6-tool polymarket family. The server also mixes unrelated domains — only 4 of 35 tools are MBTA transit tools while the rest are Pipeworx data research, prediction markets, memory, and subscriptions — making it a kitchen sink rather than a well-scoped set.

Completeness4/5

The Pipeworx research surface is thorough: query, grounded verification, deep research, entity resolution, profiles, comparisons, change feeds, claim validation, and subscriptions are all covered with few dead ends. Minor gaps exist — the MBTA portion lacks schedule/line-detail tools beyond departures and alerts, and the AI-visibility feature feels bolted on without deeper integration.

Resources