Skip to main content
Glama

Law Feeds

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).

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already indicate readOnly, openWorld, idempotent, and non-destructive behavior. The description adds significant behavioral context: it explains return structure (tracked, expired, snapshot_dates), edge decay computation, snapshot gaps, and TTL limits. 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is relatively long but front-loaded with the core purpose. Every sentence adds value and avoids fluff. Minor wordiness (e.g., full field explanations) but overall well-structured and 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?

Given no output schema, the description thoroughly explains all return fields (tracked, expired, snapshot_dates) and their subfields, including edge_pp_net time-series, trend, decay rate, and lifespan. It also covers limits and snapshot semantics, making it self-sufficient for a complex 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 fully (100% coverage). The description adds default values, valid ranges (days clamp 2-30), and clarifies 'window' as snapshot family. It provides context that the schema lacks, but the schema already gives basic descriptions.

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 provides 'edge persistence and decay telemetry' from daily snapshots. It answers a specific question about edge age and shrinkage, and it differentiates from sibling 'polymarket_edges' by focusing on time-series analysis and decay metrics.

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?

The description explains when to use: to determine if an edge is fresh or old, and what the data indicates. It implicitly guides away from using this for single-point snapshots (provided by sibling polymarket_edges). However, it lacks explicit when-not-to-use or alternative tool mentions.

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

All Law Feeds 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

Multiple tool families overlap heavily: ask_pipeworx/ask_pipeworx_beta/ask_pipeworx_grounded all route through the same 5,721 tools, polymarket_edges/polymarket_arbitrage/bet_research/polymarket_fill_risk all target prediction-market opportunities, and ai_visibility_check vs scan_competitor_ai_presence cover the same probe. An agent would struggle to pick the right one without reading every description carefully.

Naming Consistency3/5

There are coherent subfamilies (ask_pipeworx_*, polymarket_*, remember/recall/forget, list/read/fetch_feed), but the overall set mixes verb-first names (list_feeds, validate_claim, fetch_feed) with noun-first names (entity_profile, bet_research, deep_research) and adjective-led names (recent_alerts, recent_changes). The inconsistency is noticeable but not chaotic.

Tool Count2/5

34 tools is heavy for a server branded 'Law Feeds,' and many tools are off-domain (Polymarket betting, npm dependency scanning, AI visibility marketing, generic memory). The breadth could justify a larger catalog, but the overlapping research/Polymarket tools inflate the count beyond what the surface needs.

Completeness3/5

As a general data-gateway, the set is fairly complete: routing, grounded answers, deep research, entity resolution, comparison, subscriptions, memory, and feedback are all covered. Relative to the 'Law Feeds' identity, though, the surface is shallow — only list_feeds, read_feed, and fetch_feed serve that purpose, with no feed search, management, or update capabilities.

Resources