Skip to main content
Glama

Ietf Datatracker

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

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

Annotations already declare read-only and idempotent behavior, but the description adds substantial detail: snapshot write-on-cache-miss behavior, 60-day TTL, decay from daily closes not intraday, expired opportunities meaning, lifespan median as 'competition clock', and signed edge_pp_net semantics (negative = SELL YES). 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 long but every sentence is dense and informative, with clear sections (Args, RESPONSE, LIMITS) and front-loaded purpose. No filler or redundancy; each detail earns its place.

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?

There is no output schema, so the description fully shoulders the burden of explaining return values. It thoroughly describes tracked[], expired[], and snapshot_dates[] with semantics, plus limitations (TTL, snapshot start, daily-close basis). For a complex telemetry tool, this is complete.

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 with defaults and clamps. The description merely restates defaults ('default 14, max 30', 'default 1wk') and adds 'snapshot family' without new semantic value, so the baseline 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 opens with a specific verb+resource: 'Edge persistence and decay telemetry built from daily polymarket_edges snapshots.' It explicitly frames the tool's core question ('how long has this edge existed and is it shrinking?') and contrasts fresh vs. 3-week-old edges, which clearly distinguishes it from the sibling `polymarket_edges` and other market 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?

The description gives clear context for when to use the tool (historical edge persistence, distinguishing fresh vs. stale wide edges) but does not explicitly mention alternatives like `polymarket_edges` or state when not to use it. It has no exclusions, so it earns a 4 rather than a 5.

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

All Ietf Datatracker 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

B3.4/5.0
Disambiguation2/5

Several tools have overlapping or poorly distinguished purposes. For instance, `ask_pipeworx` and `ask_pipeworx_beta` have nearly identical descriptions, and `ask_pipeworx_grounded` also shares the same routing but adds a different output format. The `ai_visibility_check` and `scan_competitor_ai_presence` tools also overlap significantly.

Naming Consistency3/5

There is some consistency with verb_noun patterns (e.g., `resolve_entity`, `search_within`, `subscribe`, `unsubscribe`). However, there are many deviations: `ask_pipeworx`, `pipeworx_feedback`, `pipeworx_trending`, `entity_profile`, `scan_dependency`, and `polymarket_edges` break the pattern, mixing descriptive names with non-standard prefixes.

Tool Count4/5

37 tools is slightly above the ideal range for a single MCP server, but the tools cover a very broad and varied domain (IETF data, company research, prediction markets, package scanning, memory, etc.). The count is high but still within a manageable scope for a multi-purpose utility server.

Completeness2/5

The server combines tools from two very different domains: IETF Datatracker (document/WG/person lookups) and Pipeworx (data retrieval, prediction markets, company analysis). The IETF-related tools are sparse and incomplete (only document search, document, person, wg, wgs_search, rfc are present—no ability to create or modify records). The Pipeworx side is extensive but leaves notable gaps (e.g., no tool for submitting comments or editing IETF documents).

Resources