Skip to main content
Glama

Data Fcc

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 indicate read-only and idempotent; description adds rich behavioral detail: return structure (tracked[], expired[], snapshot_dates[]) and limits (60-day TTL, daily closes). No contradictions.

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?

Description is substantial but every sentence serves a purpose. Could be slightly more compact, but front-loaded with purpose and efficiently structured.

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, yet description fully explains returned fields (tracked, expired, snapshot_dates) and their contents, plus limitations. Sufficient for agent to use correctly.

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 with descriptions; description adds default values, clamp for days, and interprets window as snapshot family. Adds meaningful context 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?

Description clearly states it provides edge persistence and decay telemetry from daily snapshots, answering a specific question about edge age. It distinguishes a fresh wide edge from an old one, showing precise purpose and differentiation from sibling tools.

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 is for historical edge analysis, but no explicit when-not-to-use or alternatives among siblings (e.g., polymarket_edges). Context is clear but lacks exclusions.

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

All Data Fcc 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

Several tools overlap in purpose: ask_pipeworx and ask_pipeworx_beta are explicitly identical right now, and ask_pipeworx_grounded, deep_research, and validate_claim all query the same underlying data catalog in similar ways. The descriptions provide detailed usage guidance, but the query family and the five-strong Polymarket family still create real misselection risk. Memory, subscription, and FCC tools are clearly distinct.

Naming Consistency4/5

Tool names are consistently snake_case and mostly follow recognizable verb_noun or prefixed-family patterns (ask_pipeworx_*, polymarket_*, pipeworx_*). The main deviations are bare one-word names like datasets, metadata, query, remember, and forget, plus a few noun-first names like entity_profile and polymarket_arbitrage. Overall the naming is readable and predictable, with only minor inconsistencies.

Tool Count2/5

At 34 tools, this server is well past the 25+ threshold and feels overloaded. It bundles a general-purpose data-query gateway, FCC open-data access, Polymarket analytics, AI-visibility scanning, memory, subscriptions, npm dependency checks, and llms.txt generation into one surface. Each functional area is small on its own, but the combined set would be more coherent split into several focused servers.

Completeness4/5

The core data lifecycle is well covered: discovery (suggest_questions, discover_tools), single queries (ask_pipeworx), grounded/evidence-backed answers, deep multi-source research, entity resolution/profiling/comparison, change feeds, and fact-checking all exist. FCC open data has search, schema, and query tools, and subscriptions/memory have full CRUD-style coverage. Minor gaps remain (e.g., no direct pipeworx:// URI fetch tool, no enumeration of all discoverable data sources), but they do not block typical workflows.

Resources