Skip to main content
Glama

Peeringdb

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 provide readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description complements these with rich behavioral detail: response structure (tracked[], expired[], snapshot_dates[]), snapshot generation on cache-miss (gaps mean no scan), history depth bounded by 60-day TTL, decay computed from daily closes not intraday, and edge sign conventions. No contradictions 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?

The description is dense but extremely well-structured with labeled sections: purpose, args, response contract, and limitations. Every sentence conveys essential information—no fluff or redundancy. It front-loads the core question and then details response fields and caveats efficiently.

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?

Even without an output schema, the description fully specifies the response shape (tracked[], expired[], snapshot_dates[] with field meanings), explains data provenance and gaps, and covers limitations (TTL, decay basis). This is complete enough for an agent to select and invoke the tool correctly without external documentation.

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%: both days and window are fully described in the input schema. The description restates defaults and adds the phrase 'snapshot family' but does not add significant new meaning beyond what the schema already provides. Baseline of 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 states a specific verb and resource: 'Edge persistence and decay telemetry built from daily polymarket_edges snapshots.' It clearly answers the question 'how long has this edge existed and is it shrinking?' and distinguishes itself from siblings like polymarket_edges by focusing on historical persistence/decay rather than 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 Guidelines4/5

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

It gives clear context for when to use: 'a fresh wide edge and a 3-week-old wide edge are different trades.' It explains the response includes expired opportunities as a competition clock, and notes limitations like snapshot TTL. However, it does not explicitly name alternatives or exclusion criteria, so a full 5 is not earned.

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

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

Many tools overlap in purpose: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, and validate_claim all provide data retrieval with subtle differences. The Polymarket suite (arbitrage, edges, edge_tracker, fill_risk, kalshi_spread) and AI visibility tools (ai_visibility_check, scan_competitor_ai_presence) also have fuzzy boundaries. While some tools are clearly distinct, the overall set has significant ambiguity that could lead to misselection.

Naming Consistency2/5

Tool names mix conventions: some are verb_noun (search_networks, compare_entities, remember, forget), others are noun_compound (entity_profile, polymarket_edges, ask_pipeworx), and a few are verb-only (recall, forget). The pattern is inconsistent, with no clear naming strategy across the tool surface.

Tool Count2/5

With 34 tools, the server is heavily overloaded. While it serves as a general data platform, many tools are meta-level (discover_tools, suggest_questions) or peripheral (subscriptions, memory). The count feels excessive for the core purpose, and many tools could be consolidated or removed.

Completeness1/5

Despite the server name 'Peeringdb', only three tools (search_networks, search_facilities, search_exchanges) directly serve that domain. The vast majority of tools cover unrelated areas (Pipeworx data, Polymarket betting, AI visibility, memory, subscriptions). For the declared purpose of PeeringDB, the surface is severely incomplete—missing common operations like retrieving network details, viewing IX members, or managing peering policies.

Resources