Skip to main content
Glama

Macvendors

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

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

Annotations indicate readOnly, openWorld, idempotent. The description adds significant behavioral context: response structure (tracked, expired, snapshot_dates), field meanings (signed value, decay computed on absolute), limitations (60-day TTL, daily closes not intraday), and data source conditions.

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?

A single dense paragraph covering all essential aspects. Every sentence adds value, though a slightly more structured format (e.g., separating response fields) could improve readability. No superfluous text.

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?

No output schema, but description fully documents response fields and their meanings. Covers parameters, limitations, data source behavior, and usage context. Complete for a read-only analytics 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 covers both parameters, but description adds useful specifics: default values, clamp range for days, and explains window as 'snapshot family'. This adds meaning beyond the 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 explicitly states the tool's purpose: edge persistence and decay telemetry. It answers 'how long has this edge existed and is it shrinking?' and distinguishes it from sibling tool polymarket_edges by focusing on historical time-series and trend analysis.

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

Usage Guidelines5/5

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

Provides clear guidance on when to use: comparing fresh vs. old edges. Implicitly contrasts with polymarket_edges (raw edges). Includes example scenario to illustrate the tool's value.

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

All Macvendors 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.8/5.0
Disambiguation2/5

Several tools have heavily overlapping purposes: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded share the same router, with the beta variant currently identical to stable. The five polymarket_* tools plus bet_research also blur boundaries, and discover_tools/suggest_questions both serve discovery. Detailed descriptions help, but an agent could easily select the wrong tool.

Naming Consistency3/5

All names use lower_snake_case and many follow a clear verb_noun pattern (resolve_entity, validate_claim, generate_llms_txt). However, there are notable deviations: entity_profile, pipeworx_feedback, polymarket_edges, recent_changes, and bet_research lead with nouns or adjectives. The style is readable and predictable in clusters, but not uniform.

Tool Count2/5

32 tools is well above the 25+ threshold for 'too many', and the server name Macvendors suggests a narrow MAC-lookup service, yet most tools belong to a much broader Pipeworx data/prediction-market platform. Several tools are near-duplicates or micro-variants (three ask_pipeworx versions, six polymarket tools). The set would be more appropriately split or heavily consolidated.

Completeness4/5

Within the actual broad research platform domain, the surface is fairly complete: discovery, routing, grounded answers, entity profiles, comparisons, recent changes, claim validation, semantic search, prediction-market analysis, subscriptions, memory, and feedback are all covered. Minor gaps exist, such as no subscription update tool and no batch MAC lookup, but agents can generally complete workflows without dead ends.

Resources