Skip to main content
Glama

W3c

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?

Annotations already declare read-only, idempotent, non-destructive. Description adds details: reads snapshots, returns tracked, expired, snapshot_dates, and explains data derivation (decay from daily closes). No contradiction.

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?

Well-structured: purpose, response fields (tracked, expired, snapshot_dates), then limitations. Slightly verbose but every sentence is informative.

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 thoroughly explains the response structure (tracked[] with time-series, expired[], snapshot_dates[]) and limitations. Covers inputs, outputs, and context comprehensively.

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?

Both parameters have schema descriptions (100% coverage). Description adds context like default and max for days, enumeration for window. Schema already covers well, so description adds marginal value.

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 the tool provides edge persistence and decay telemetry from daily snapshots, answering 'how long has this edge existed and is it shrinking?'. It clearly distinguishes from sibling polymarket_edges by focusing on time-series analysis.

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?

Implied usage: compare fresh vs old edges. Limitations noted (60-day TTL, daily closes). No explicit when-not-to-use or alternatives, but context is sufficient.

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

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

The three ask_pipeworx variants plus deep_research and validate_claim overlap heavily on the same routing capability — ask_pipeworx_beta is even explicitly identical to ask_pipeworx right now. The polymarket tools (arbitrage/edges/edge_tracker/fill_risk/kalshi_spread) form a second cluster with fuzzy boundaries, and ai_visibility_check vs scan_competitor_ai_presence overlap. However, most other tools (w3c_search, spec, remember/recall/forget, subscribe/unsubscribe) have clear distinct roles.

Naming Consistency3/5

Names are generally descriptive snake_case with recognizable prefix families (ask_pipeworx_*, polymarket_*, w3c_*), but verb usage is inconsistent: passive labels like ai_visibility_check and entity_profile sit alongside imperatives like recall, forget, subscribe, and resolve_. There's no uniform verb_noun or noun_pattern convention across the set.

Tool Count2/5

33 tools is over the heavy threshold, and the count is wildly mismatched to the server's claimed identity: the server is named 'W3c' yet only 2 of 33 tools (w3c_search, w3c_spec) relate to W3C. The remaining 31 form a sprawling Pipeworx data/prediction-market service that would justify its own server, making this aggregation incoherent.

Completeness3/5

For its actual purpose (broad data research + prediction markets), the surface is fairly complete: search, grounded answers, deep research, comparison, entity profiles, entity resolution, memory, subscriptions, and feedback cover the main workflows. But for the server's stated W3C purpose, only search and spec-detail exist with no broader standards tooling. The domain mismatch makes completeness hard to credit.

Resources